Build bundle on MR and default branch pipelines
What does this MR do?
Build bundle on MR and default branch pipelines
- Build bundle and catalog image on on default branch and MR pipelines.
- The images are pushed to a staging repository, while release/tag pipelines keep pushing to the non-staging repository
- Removed Go cache setup which is not needed for bundle building
This helps us to validate that our CI Podman setup and bundle building is working outside of the release pipelines.
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion.
Required
-
Merge Request Title and Description are up to date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline on GitLab.com -
When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes -
Documentation created/updated -
Tests added -
Integration tests added to GitLab QA -
Equivalent MR/issue for omnibus-gitlab opened -
Validate potential values for new configuration settings. Formats such as integer 10
, duration10s
, URIscheme://user:passwd@host:port
may require quotation or other special handling when rendered in a template and written to a configuration file.
Related issues
Closes #1697 (closed)
Edited by Clemens Beck