[BE] Provide script to run on console for bulk assignment
Purpose of this MR
- The current MR presents the
Code Suggestions Bulk User Assignment
rake task. - The script accepts a CSV file path as a parameter and handles user assignments.
- This task is specifically designated for manual use and not automated or running within the GitLab codebase.
Local Setup and Validation Instructions
For details on setting up and validating the script locally, kindly document the file in the MR.
Related to #431619
Merge request reports
Activity
changed milestone to %16.9
assigned to @mhamda
- Resolved by Bishwa Hang Rai
- Resolved by Vijay Hawoldar
7 Warnings 7b19bc10: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines. 0103a6ef: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines. ed755a24: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines. ed755a24: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines. cdf6bf56: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines. 4c36e394: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines. f70090f5: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines. 1 Message 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. Documentation review
The following files require a review from a technical writer:
-
doc/raketasks/user_management.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
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 @joseph
(UTC+0, 1 hour behind author)
@engwan
(UTC+8, 7 hours ahead of author)
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.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger-
- Resolved by Bishwa Hang Rai
@bhrai, I suggest we review this script to determine the best course of action—whether to include it in the documentation or provide it upon request. Could you kindly review it?
requested review from @bhrai
- Resolved by Mohamed Hamda
- Resolved by Mohamed Hamda
- Resolved by Mohamed Hamda
- Resolved by Mohamed Hamda
added 2 commits
- A deleted user
added documentation label
- Resolved by Bishwa Hang Rai
E2E Test Result Summary
allure-report-publisher
generated test report!e2e-test-on-gdk:
test report for d676f8edexpand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Create | 8 | 0 | 3 | 0 | 11 | ✅ | | Govern | 3 | 0 | 0 | 0 | 3 | ✅ | | Monitor | 4 | 0 | 0 | 0 | 4 | ✅ | | Plan | 4 | 0 | 0 | 0 | 4 | ✅ | | Package | 0 | 0 | 1 | 0 | 1 | ➖ | | Data Stores | 2 | 0 | 0 | 0 | 2 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 21 | 0 | 4 | 0 | 25 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
- Resolved by Vijay Hawoldar
@bhrai Added specs and they are now green, do you mind having another look?
requested review from @bhrai
- Resolved by Bishwa Hang Rai
- Resolved by Bishwa Hang Rai
requested review from @fneill
- Resolved by Bishwa Hang Rai
- Resolved by Vijay Hawoldar
- Resolved by Bishwa Hang Rai
- Resolved by Mohamed Hamda
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
requested review from @fneill
requested review from @bhrai
- Resolved by Bishwa Hang Rai
- Resolved by Bishwa Hang Rai
- Resolved by Bishwa Hang Rai
- Resolved by Bishwa Hang Rai
- Resolved by Vijay Hawoldar
- Resolved by Bishwa Hang Rai
- Resolved by Bishwa Hang Rai
added 2 commits
requested review from @bhrai
requested review from @vij
- Resolved by Vijay Hawoldar
@bhrai
, thanks for approving this merge request.This is the first time the merge request has been approved. To ensure we don't only run predictive pipelines, and we don't break
master
, a new pipeline will be started shortly.Please wait for the pipeline to start before resolving this discussion and set auto-merge for the new pipeline. See merging a merge request for more details.
added pipeline:mr-approved label
@mhamda Some end-to-end (E2E) tests should run based on the stage label.
Please start the
trigger-omnibus-and-follow-up-e2e
job in theqa
stage and wait for the tests in thefollow-up-e2e:package-and-test-ee
pipeline to pass before merging this MR. Do not use Auto-merge, unless these tests have already completed successfully, because a failure in these tests do not block the auto-merge. (E2E tests are computationally intensive and don't run automatically for every push/rebase, so we ask you to run this job manually at least once.)To run all E2E tests, apply the pipeline:run-all-e2e label and run a new pipeline.
E2E test jobs are allowed to fail due to flakiness. See current failures at the latest pipeline triage issue.
Once done, apply the
emoji on this comment.Team members only: for any questions or help, reach out on the internal
#test-platform
Slack channel.- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
removed review request for @vij
Quarantined Fulfillment QA E2E Tests
The following Fulfillment QA E2E tests are in quarantine. If your changes would be covered by these tests, please be sure to perform manual testing.
Description Location Fulfillment with existing compute minutes packs behaves like Purchase storage adds additional storage to group namespace ./qa/specs/features/ee/browser_ui/11_fulfillment/purchase/purchase_storage_spec.rb[1:3:1:1] Fulfillment with an active subscription behaves like Purchase storage adds additional storage to group namespace ./qa/specs/features/ee/browser_ui/11_fulfillment/purchase/purchase_storage_spec.rb[1:2:1:1] Fulfillment without active subscription behaves like Purchase storage adds additional storage to group namespace ./qa/specs/features/ee/browser_ui/11_fulfillment/purchase/purchase_storage_spec.rb[1:1:1:1] requested review from @vij
Hi
@fneill
,GitLab Bot has added the Technical Writing label because a Technical Writer has approved or merged this MR.
This message was generated automatically. You're welcome to improve it.
added Technical Writing label
removed review request for @fneill
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
- Resolved by Vijay Hawoldar
removed review request for @vij
Quarantined Fulfillment QA E2E Tests
The following Fulfillment QA E2E tests are in quarantine. If your changes would be covered by these tests, please be sure to perform manual testing.
Description Location Fulfillment without active subscription behaves like Purchase storage adds additional storage to group namespace ./qa/specs/features/ee/browser_ui/11_fulfillment/purchase/purchase_storage_spec.rb[1:1:1:1] Fulfillment with existing compute minutes packs behaves like Purchase storage adds additional storage to group namespace ./qa/specs/features/ee/browser_ui/11_fulfillment/purchase/purchase_storage_spec.rb[1:3:1:1] Fulfillment with an active subscription behaves like Purchase storage adds additional storage to group namespace ./qa/specs/features/ee/browser_ui/11_fulfillment/purchase/purchase_storage_spec.rb[1:2:1:1] requested review from @vij
removed review request for @bhrai
mentioned in issue mhamda/personal_development_progress#4
- Resolved by Vijay Hawoldar
removed review request for @vij
mentioned in commit d676f8ed
requested review from @vij
Quarantined Fulfillment QA E2E Tests
The following Fulfillment QA E2E tests are in quarantine. If your changes would be covered by these tests, please be sure to perform manual testing.
Description Location Fulfillment with an active subscription behaves like Purchase storage adds additional storage to group namespace ./qa/specs/features/ee/browser_ui/11_fulfillment/purchase/purchase_storage_spec.rb[1:2:1:1] Fulfillment without active subscription behaves like Purchase storage adds additional storage to group namespace ./qa/specs/features/ee/browser_ui/11_fulfillment/purchase/purchase_storage_spec.rb[1:1:1:1] Fulfillment with existing compute minutes packs behaves like Purchase storage adds additional storage to group namespace ./qa/specs/features/ee/browser_ui/11_fulfillment/purchase/purchase_storage_spec.rb[1:3:1:1] enabled an automatic merge when all merge checks for d676f8ed pass
enabled an automatic merge when all merge checks for d676f8ed pass
mentioned in commit eca41ca2
added workflowstaging-canary label and removed workflowin dev label
added workflowcanary label and removed workflowstaging-canary label
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
added releasedcandidate label
mentioned in issue #501110