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 via a [Gitlab CI](https://gitlab.suse.de/qac/blue-moon-launcher) individually and are not yet integrated into the container-release-bot pipeline. For IBM HPVS testing our busybox containers, we schedule the need to integrate those test runs after those images are released because we cannot access registry.suse.de. into the container-release-bot. See https://gitlab.suse.de/qac/container-release-bot/-/issues/20 - this is about adding post-release triggers We probably need to add the container-release-bot 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 post-release triggers, i.e. triggering custom multiple openQA test runs AFTER a products instead of just one (per container is released definition) * **AC2** : For the busybox BCI containers, we also schedule openQA test runs for the IBM HPVS after HPVS, but those containers are released Note that post-release triggers should only schedule openQA test runs. They do not need to observe them, or wait for them to pass. The aim is only scheduling. blocking the release pipeline ## Further References * https://confluence.suse.com/display/qasle/IBM+Hyper+Protect+Virtual+Server+Cloud * https://gitlab.suse.de/qac/container-release-bot/ * https://gitlab.suse.de/qac/container-release-bot/-/issues/20 https://gitlab.suse.de/qac/container-release-bot/-/issues/19 * https://gitlab.suse.de/qac/blue-moon-launcher