Revert "Merge branch 'sc1-upgrade-sidekiq-gem-only' into 'master'"
Purpose of revert
Revert !135185 (merged) to unblock gitlab-com/gl-infra/production#17158 (closed)
Checklist
- [-] Create an issue to reinstate the merge request and assign it to the author of the reverted merge request.
- [-] If the revert is to resolve a broken 'master' incident, please read through the Responsibilities of the Broken
master
resolution DRI. - [-] If the revert involves a database migration, please read through Deleting existing migrations.
-
Add the appropriate labels before the MR is created. We can skip CI/CD jobs only if the labels are added before the CI/CD pipeline is created.
Milestone info
-
I am reverting something in the current milestone. No changelog is needed, and I've added a ~"regression:*"
label. -
I am reverting something in a different milestone. A changelog is needed, and I've removed the ~"regression:*"
label.
Related issues and merge requests
Merge request reports
Activity
added master:broken pipeline:expedite labels
- Resolved by Mayra Cabrera
I've prepared a revert of !135185 (merged) in case it is needed for gitlab-com/gl-infra/production#17158 (closed)
Edited by Mayra Cabrera
- A deleted user
added backend label
- Resolved by Mayra Cabrera
- Resolved by Mayra Cabrera
3 Warnings This merge request is quite big (797 lines changed), please consider splitting it into multiple merge requests. This merge request does not have any assignee yet. Setting an assignee clarifies who needs to take action on the merge request at any given time. This merge request does not refer to an existing milestone. 1 Message CHANGELOG missing: If this merge request needs a changelog entry, add the
Changelog
trailer to the commit message you want to add to the changelog.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 @ddieulivol
(UTC+1, 7 hours ahead of author)
@proglottis
(UTC+13, 19 hours ahead of author)
test for spec/features/*
@ddieulivol
(UTC+1, 7 hours ahead of author)
Maintainer review is optional for test for spec/features/*
Please check reviewer's status!
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.
Rubygems
This merge request adds, or changes a Rubygems dependency. Please review the Gemfile guidelines.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger- Resolved by 🤖 GitLab Bot 🤖
Proper labels assigned to this merge request. Please ignore me.
@mayra-cabrera - please see the following guidance and update this merge request.1 Error Please add typebug typefeature, or typemaintenance label to this merge request. Edited by 🤖 GitLab Bot 🤖
added typebug label
mentioned in issue gitlab-com/gl-infra/production#17158 (closed)
assigned to @mayra-cabrera
requested review from @stomlinson
added Pick into auto-deploy severity2 labels
LGTM, thanks @mayra-cabrera
mentioned in commit 8cf82c93
Successfully picked into
16-7-auto-deploy-2023112020
.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 https://gitlab.com/gitlab-org/gitlab/-/merge_requests/137444
removed Pick into auto-deploy label