Promote test to reliable
What does this MR do and why?
Describe in detail what your merge request does and why.
Promotes Kubernetes Agent end to end test to the reliable test suite. Runs only in staging pipelines.
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 %14.9
assigned to @svistas
marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed
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.
If needed, you can retry the
danger-review
job that generated this comment.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 QA Erick Banks ( @ebanks
) (UTC-8, 10 hours behind@svistas
)Chloe Liu ( @chloeliu
) (UTC-8, 10 hours behind@svistas
)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.
Generated by
Dangermentioned in issue #351218 (closed)
The
package-and-qa
job from pipeline https://gitlab.com/gitlab-org/gitlab/-/pipelines/486189201 triggered https://gitlab.com/gitlab-org/build/omnibus-gitlab-mirror/-/pipelines/486195910 downstream.The
gitlab-qa
downstream pipeline passed. .This is a test running only against staging, triggered a pipeline to validate the change
Allure report
allure-report-publisher
generated test report for ad02647c!review-qa-smoke:
test report
review-qa-reliable: test report
package-and-qa: test report
review-qa-all: test reportcc @Alexand
requested review from @ebanks
added sectionops label
@chloeliu, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline is more than 2 hours old, you should:
- Ensure the merge request is not in Draft status.
- Start a pipeline. (Especially important for Community contribution merge requests.)
- Set the merge request to merge when pipeline succeeds.
mentioned in commit 3342d32b
added workflowstaging-canary label
added workflowstaging label and removed workflowstaging-canary label
added workflowcanary label and removed workflowstaging label
added workflowproduction label and removed workflowcanary label
mentioned in issue gitlab-com/gl-infra/delivery#2280 (closed)
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label
added groupenvironments label and removed groupconfigure [DEPRECATED] label