Rename `generate_test_file` feature flag
What does this MR do and why?
Rename generate_test_file
feature flag
This renames the generate_test_file
feature flag to generate_test_file_flag
to prevent a naming conflict with the licensed feature name.
Original feature flag was introduced in !118365 (merged)
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
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
assigned to @phikai
added devopscreate groupcode review sectiondev typemaintenance labels
- A deleted user
added backend feature flag labels
1 Warning 175b7b3a: The commit body should not contain more than 72 characters per line. For more information, take a look at our Commit message guidelines. 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 Sam Kim (
@samsam_kim
) (UTC-7)Jarka Košanová (
@jarka
) (UTC+2)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 maintenancerefactor label
mentioned in issue #409180 (closed)
mentioned in commit gitlab-org-sandbox/gitlab-jh-validation@717691b4
@dgruzd
, thanks for approving this merge request.This is the first time the merge request is approved. To ensure full test coverage, a new pipeline will be started shortly.
For more info, please refer to the following links:
added pipeline:mr-approved label
requested review from @dgruzd
marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed
changed milestone to %16.0
enabled an automatic merge when the pipeline for 009440cc succeeds
mentioned in commit gitlab-org-sandbox/gitlab-jh-validation@009440cc
added customer-critical-merge-request label
Allure report
allure-report-publisher
generated test report!e2e-package-and-test:
test report for 175b7b3aexpand test summary
+-----------------------------------------------------------------------+ | suites summary | +------------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +------------------+--------+--------+---------+-------+-------+--------+ | Create | 262 | 0 | 42 | 0 | 304 | ✅ | | Plan | 150 | 0 | 0 | 0 | 150 | ✅ | | Verify | 108 | 0 | 8 | 0 | 116 | ✅ | | Package | 0 | 0 | 6 | 0 | 6 | ➖ | | Monitor | 16 | 0 | 4 | 0 | 20 | ✅ | | Secure | 6 | 0 | 18 | 0 | 24 | ✅ | | Govern | 91 | 1 | 0 | 0 | 92 | ❌ | | Manage | 66 | 0 | 6 | 0 | 72 | ✅ | | Fulfillment | 4 | 0 | 50 | 0 | 54 | ✅ | | Framework sanity | 0 | 0 | 2 | 0 | 2 | ➖ | | Data Stores | 68 | 0 | 0 | 0 | 68 | ✅ | | Release | 12 | 0 | 0 | 0 | 12 | ✅ | | Analytics | 4 | 0 | 0 | 0 | 4 | ✅ | | Growth | 0 | 0 | 4 | 0 | 4 | ➖ | | Configure | 0 | 0 | 6 | 0 | 6 | ➖ | | ModelOps | 0 | 0 | 2 | 0 | 2 | ➖ | +------------------+--------+--------+---------+-------+-------+--------+ | Total | 787 | 1 | 148 | 0 | 936 | ❌ | +------------------+--------+--------+---------+-------+-------+--------+
mentioned in commit cf7172c4
added Pick into auto-deploy severity2 labels
Successfully picked into
16-0-auto-deploy-2023050115
.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 cac82f17
removed Pick into auto-deploy label
mentioned in merge request !119225 (merged)
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added releasedcandidate label
mentioned in epic &10524