Draft: Test 14-4-3
What does this MR do and why?
Test 14-4-3
DO NOT MERGE
gitlab-org/release/tasks#3186 (closed)
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
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 @hphilipps
mentioned in issue gitlab-org/release/tasks#3186 (closed)
- A deleted user
added 1 deleted label
1 Error a5de1d15: The commit subject must start with a capital letter. For more information, take a look at our Commit message guidelines. 4 Warnings a5de1d15: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines. Please add a merge request type to this merge request. This merge request does not refer to an existing milestone. Most of the time, merge requests should target master
. Otherwise, please set the relevantPick into X.Y
label.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.
Pipeline Changes
This merge request contains changes to the pipeline configuration for the GitLab project.
Please consider the effect of the changes in this merge request on the following:
- Effects on different pipeline types
- Effects on non-canonical projects:
gitlab-foss
security
dev
- personal forks
- Effects on pipeline performance
Please consider communicating these changes to the broader team following the communication guideline for pipeline changes
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 tooling for CI, Danger Kyle Wiebers ( @kwiebers
) (UTC-6, 7 hours behind@hphilipps
)Rémy Coutable ( @rymai
) (UTC+1, same timezone as@hphilipps
)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
DangerThe
package-and-qa
job from pipeline https://gitlab.com/gitlab-org/gitlab/-/pipelines/420181622 triggered https://gitlab.com/gitlab-org/build/omnibus-gitlab-mirror/-/pipelines/420208171 downstream.The
qa-test
job from pipeline https://gitlab.com/gitlab-org/build/omnibus-gitlab-mirror/-/pipelines/420208171 triggered https://gitlab.com/gitlab-org/gitlab-qa-mirror/-/pipelines/420267889 downstream.The
gitlab-qa
downstream pipeline failed! .
Allure report
allure-report-publisher
generated test report for a5de1d15!package-and-qa:
test report