danger-review
Passed Started
by
@mkarampalas
Michael Karampalas
1Running with gitlab-runner 13.10.0-rc1 (ecc4c590)2 on prm-com-gitlab-org ae3bfce23 feature flags: FF_GITLAB_REGISTRY_HELPER_IMAGE:true6Using Docker executor with image registry.gitlab.com/gitlab-org/gitlab-build-images:ruby-2.7.2.patched-golang-1.14-git-2.29-lfs-2.9-chrome-89-node-14.15-yarn-1.22-postgresql-11-graphicsmagick-1.3.36 ...7Authenticating with credentials from job payload (GitLab Registry)8Pulling docker image registry.gitlab.com/gitlab-org/gitlab-build-images:ruby-2.7.2.patched-golang-1.14-git-2.29-lfs-2.9-chrome-89-node-14.15-yarn-1.22-postgresql-11-graphicsmagick-1.3.36 ...9Using docker image sha256:3d9eaa64e5ac84c87745afcb0e240b69c313eebf624092e623f9fb5aee0f49b7 for registry.gitlab.com/gitlab-org/gitlab-build-images:ruby-2.7.2.patched-golang-1.14-git-2.29-lfs-2.9-chrome-89-node-14.15-yarn-1.22-postgresql-11-graphicsmagick-1.3.36 with digest registry.gitlab.com/gitlab-org/gitlab-build-images@sha256:f5fca6fbad34f17ebac8b436990cc1cd97ca47a61c1d3ba9aa3dd3081e4a9f6a ...11Running on runner-ae3bfce2-project-278964-concurrent-0 via runner-ae3bfce2-prm-1616415722-48207845...13$ eval "$CI_PRE_CLONE_SCRIPT"14Downloading archived master...15Connecting to storage.googleapis.com (172.217.193.128:443)16saving to '/tmp/gitlab.tar.gz'17gitlab.tar.gz 6% |** | 26.9M 0:00:14 ETA18gitlab.tar.gz 60% |******************* | 250M 0:00:01 ETA19gitlab.tar.gz 100% |********************************| 411M 0:00:00 ETA20'/tmp/gitlab.tar.gz' saved21Extracting tarball into /builds/gitlab-org/gitlab...22Fetching changes with git depth set to 20...23Reinitialized existing Git repository in /builds/gitlab-org/gitlab/.git/24remote: Enumerating objects: 175, done. 25remote: Counting objects: 100% (144/144), done. 26remote: Compressing objects: 100% (52/52), done. 27remote: Total 63 (delta 47), reused 22 (delta 10), pack-reused 0 29 * [new ref] 61f496dba89bdbbd3ace783d5754a8846cd7e6d0 -> refs/pipelines/27437952430Checking out 61f496db as refs/merge-requests/57119/merge...31Skipping Git submodules setup33Checking cache for danger-review-v1-3...34Downloading cache.zip from https://storage.googleapis.com/gitlab-com-runners-cache/project/278964/danger-review-v1-3 35WARNING: vendor/ruby/2.7.0/gems/deprecation_toolkit-1.5.1/gemfiles/test/deprecations: chmod vendor/ruby/2.7.0/gems/deprecation_toolkit-1.5.1/gemfiles/test/deprecations: no such file or directory (suppressing repeats) 36Successfully extracted cache38Using docker image sha256:3d9eaa64e5ac84c87745afcb0e240b69c313eebf624092e623f9fb5aee0f49b7 for registry.gitlab.com/gitlab-org/gitlab-build-images:ruby-2.7.2.patched-golang-1.14-git-2.29-lfs-2.9-chrome-89-node-14.15-yarn-1.22-postgresql-11-graphicsmagick-1.3.36 with digest registry.gitlab.com/gitlab-org/gitlab-build-images@sha256:f5fca6fbad34f17ebac8b436990cc1cd97ca47a61c1d3ba9aa3dd3081e4a9f6a ...39$ source ./scripts/utils.sh40$ run_timed_command "bundle install --jobs=$(nproc) --path=vendor --retry=3 --quiet --with danger"41$ bundle install --jobs=2 --path=vendor --retry=3 --quiet --with danger42[DEPRECATED] The `--with` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set with 'danger'`, and stop using this flag43==> 'bundle install --jobs=2 --path=vendor --retry=3 --quiet --with danger' succeeded in 1 seconds.44$ run_timed_command "retry yarn install --frozen-lockfile"45$ retry yarn install --frozen-lockfile46yarn install v1.22.547[1/5] Validating package.json...48[2/5] Resolving packages...49success Already up-to-date.50$ node ./scripts/frontend/postinstall.js51success Dependency postinstall check passed.52Done in 1.09s.53==> 'retry yarn install --frozen-lockfile' succeeded in 2 seconds.54$ run_timed_command "bundle exec danger --fail-on-errors=true --verbose"55$ bundle exec danger --fail-on-errors=true --verbose56danger/feature_flag/Dangerfile:4: warning: already initialized constant Danger::Dangerfile::SEE_DOC57danger/changelog/Dangerfile:6: warning: previous definition of SEE_DOC was here58danger/feature_flag/Dangerfile:6: warning: already initialized constant Danger::Dangerfile::SUGGEST_MR_COMMENT59danger/changelog/Dangerfile:8: warning: previous definition of SUGGEST_MR_COMMENT was here60danger/roulette/Dangerfile:5: warning: already initialized constant Danger::Dangerfile::MESSAGE61danger/pipeline/Dangerfile:3: warning: previous definition of MESSAGE was here62Results:63Messages:64- [ ] This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is **recommended**. Reviews can happen after you merge.65Markdown:66## Documentation review67The following files require a review from a technical writer:68* `data/whats_new/202103220001_13_10.yml`69The review does not need to block merging this merge request. See the:70- [Metadata for the `*.md` files](https://docs.gitlab.com/ee/development/documentation/#metadata) that you've changed. The first few lines of each `*.md` file identify the stage and group most closely associated with your docs change.71- The [Technical Writer assigned](https://about.gitlab.com/handbook/engineering/technical-writing/#designated-technical-writers) for that stage and group.72- [Documentation workflows](https://docs.gitlab.com/ee/development/documentation/workflow.html) for information on when to assign a merge request for review.73**If needed, you can retry the [`danger-review` job](https://gitlab.com/gitlab-org/gitlab/-/jobs/1117428446) that generated this comment.**74==> 'bundle exec danger --fail-on-errors=true --verbose' succeeded in 4 seconds.76Not uploading cache danger-review-v1-3 due to policy78Job succeeded