Patch release pipeline: Verify Omnibus packages are published
What does this MR do and why?
Describe in detail what your merge request does and why.
Content
- Patch release pipeline: Verify Omnibus packages are published
Add a job to the patch release pipeline to check if the Omnibus packages are released.
Since this is patch release, each of the three versions are checked one by one.
Ref: gitlab-com/gl-infra/delivery#20430 (closed)
Testing
Pipeline creation
This was tested in this repo (gitlab-org/release-tools
), just to see that the pipeline gets created as we expect it.
With |
With |
---|---|
The new job |
As you can see, when creating just verify steps, the |
Configuration testing
This was to test the configuration of the pipeline (the job order).
Checking the dependencies between jobs, we see that security_release_verify:start
depends on security_release_publish:generate_jobs
job. So, 30 minutes after the packages are published, the verification starts.
Execution testing
This MR does not implement a new execution logic. It was done in !3333 (merged).