Add Manual Omnibus and follow up e2e jobs
What does this MR do and why?
Background
In !122896 (merged), we introduced a message/comment that would ask to start e2e:package-and-test-ee
job on MR when selective e2e tests are detected. However, we came to know that in order to start e2e:package-and-test-ee
job, the user would need to first start trigger-omnibus-env
manually, then trigger-omnibus
and then e2e:package-and-test-ee
. This was bad UX. See this Slack thread (internal link) for the feedback and context. We decided to disable the message until we found a way to tie those jobs together so that they would run with once click.
Changes in this MR
This MR adds new manual wrapper jobs that would trigger Omnibus and e2e:package-and-test-ee as an automatic follow-up (Thanks @godfat-gitlab for the suggestion).
Also makes trigger-omnibus-env job automatic.
Related to: https://gitlab.com/gitlab-com/gitlab-OKRs/-/work_items/2295
This would also help resolve this issue: #416304 (closed)
Test
This was tested here: !126962 (closed)
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally.
This cannot be validated locally. It was tested here: !126962 (closed)
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.