Revert "Merge branch 'remove-transform_from_yaml_variables' into 'master'"
What does this MR do and why?
gitlab-com/gl-infra/production#7618 (closed)
Revert of !94778 (merged)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Merge request reports
Activity
changed milestone to %15.4
added backend bugfunctional grouppipeline authoring typebug labels
assigned to @furkanayhan
marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed
Suggested Reviewers (beta)
The individuals below may be good candidates to participate in the review based on various factors.
You can use slash commands in comments to quickly assign
/assign_reviewer @user1
.Suggested Reviewers @marcel.amirault
,@smcgivern
,@mbobin
,@fabiopitino
,@furkanayhan
If you do not believe these suggestions are useful, please apply the label Bad Suggested Reviewer. You can also provide feedback for this feature on this issue:
https://gitlab.com/gitlab-org/gitlab/-/issues/357923
.Automatically generated by Suggested Reviewers Bot - an experimental ML-based recommendation engine created by ~"group::applied ml".
1 Warning This merge request changed CI config files but did not update the schema. Please consider updating the schema to reflect these changes: lib/gitlab/ci/config/entry/processable.rb
lib/gitlab/ci/config/entry/variables.rb
-
spec/lib/gitlab/ci/config/entry/root_spec.rb
.
Refer to the docs for help on how to run and write specs for the CI schema.
1 Message CHANGELOG missing: If you want to create a changelog entry for GitLab FOSS, add the
Changelog
trailer to the commit message you want to add to the changelog.If you want to create a changelog entry for GitLab EE, also add the
EE: true
trailer to your commit message.If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.
Reviewer roulette
Changes that require review have been detected!
Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:
Category Reviewer Maintainer backend Serhii Yarynovskyi ( @syarynovskyi
) (UTC+3, 1 hour ahead of@furkanayhan
)Doug Stull ( @dstull
) (UTC-4, 6 hours behind@furkanayhan
)To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Dangeradded severity2 label
added Pick into auto-deploy label
changed milestone to %15.3
added Pick into 15.3 label
enabled an automatic merge when the pipeline for ca1c1b5e succeeds
mentioned in issue gitlab-com/gl-infra/production#7618 (closed)
Allure report
allure-report-publisher
generated test report!review-qa-blocking:
test report for 7ced80f3expand test summary
+-----------------------------------------------------------------------------------------+ | suites summary | +------------------------------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +------------------------------------+--------+--------+---------+-------+-------+--------+ | Plan | 47 | 0 | 1 | 47 | 48 | ❗ | | Create | 28 | 0 | 1 | 28 | 29 | ❗ | | Verify | 12 | 0 | 1 | 12 | 13 | ❗ | | Manage | 46 | 0 | 3 | 37 | 49 | ❗ | | Configure | 0 | 0 | 1 | 0 | 1 | ➖ | | Package | 0 | 0 | 1 | 0 | 1 | ➖ | | Secure | 2 | 0 | 0 | 2 | 2 | ❗ | | Protect | 2 | 0 | 0 | 2 | 2 | ❗ | | Version sanity check | 0 | 0 | 1 | 0 | 1 | ➖ | | Feature flag handler sanity checks | 9 | 0 | 0 | 9 | 9 | ❗ | +------------------------------------+--------+--------+---------+-------+-------+--------+ | Total | 146 | 0 | 9 | 137 | 155 | ❗ | +------------------------------------+--------+--------+---------+-------+-------+--------+
mentioned in commit d4926ed3
mentioned in issue #371100 (closed)
Successfully picked into
15-3-auto-deploy-2022081809
.This merge request will receive additional notifications as it's deployed. You can also use the following chatops command to check its status:
/chatops run auto_deploy status b042e43b
removed Pick into auto-deploy label
mentioned in merge request !95692 (merged)
added Pick into auto-deploy label
Successfully picked into
15-3-auto-deploy-2022081812
.This merge request will receive additional notifications as it's deployed. You can also use the following chatops command to check its status:
/chatops run auto_deploy status 3c063426
removed Pick into auto-deploy label
- Resolved by Furkan Ayhan
@rpereira2 Just curious... What's the reason why we added another Pick into auto-deploy after a "Successfully picked into" message
Edited by Furkan Ayhan
mentioned in merge request !95701 (merged)
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
mentioned in commit 3cba3e83
mentioned in issue gitlab-org/release/tasks#4176 (closed)
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-staging label and removed workflowproduction label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
mentioned in issue gitlab-com/chatops#127 (moved)
removed Pick into 15.3 label
Removed the Pick into 15.3 label since this MR has been included in 15.3.
mentioned in issue gitlab-com/gl-infra/delivery#2549
mentioned in merge request !97040 (closed)
mentioned in merge request !97043 (merged)
mentioned in issue #353991 (closed)
mentioned in merge request !97478 (merged)
mentioned in merge request !97535 (merged)
added releasedcandidate label
added devopsverify sectionops labels