action #175392
Updated by ph03nix about 1 month ago
#163190 implemented test runs running on the IBM Hyper Protect Virtual Servers. Those jobs are triggered individually and are not yet integrated into the container-release-bot pipeline.
For our busybox containers, we need to integrate those test runs into the container-release-bot.
We probably need to add the ability to schedule multiple openQA products to crb. It would be nice to have an `optional` tag to mark some of those jobs as non-blocking, i.e. the pipeline will not consider them as blockers for the release.
## Acceptance criteria
* **AC1** : The crb allows configuration of multiple openQA products instead of just one (per container definition)
* **AC2** : For the busybox BCI containers, we also schedule openQA test runs for the IBM HPVS, but those are not blocking the release pipeline
## References
* https://gitlab.suse.de/qac/container-release-bot/
* https://gitlab.suse.de/qac/container-release-bot/-/issues/19
* https://gitlab.suse.de/qac/blue-moon-launcher