action #110307
closedcoordination #110304: [epic] Enable test & release process on the container bot for BCI 15-SP4 images
15-SP4 bci-base image tested from SUSE:SLE-15-SP4:GA:TEST
0%
Description
Currently, we have enabled 15-SP4 BASE image in the container release bot:
https://gitlab.suse.de/qac/container-release-bot/-/merge_requests/34/diffs
with the regular workflow where CR is relaesed to CR:ToTest and then published to SUSE:Containers:SLE-SERVER:15-SP4.
However, this breaks the release milestone workflow we have for SLES products that are not GA yet.
SLES milestones for 15-SP4 SHOULD released by autobuild for each milestone after getting feedback from openQA's results.
15-SP4 Base image shouldn't be different.
Since we only want to trigger the tests when there are new builds in SUSE:SLE-15-SP4:GA:TEST and not run any osc command, it's better to use OBS sync instead of using the bot.
Otherwise, we would need to adapt the bot to only trigger tests from single project. This is actually what OBS sync does. Also, this way, we will prevent publishing the container ourself and leave this to autobuild team.
CONTAINER_IMAGE_TO_TEST=registry.suse.de/suse/sle-15-sp4/ga/test/images/suse/sle15:15.4
Updated by jlausuch about 2 years ago
- Status changed from Workable to In Progress
Removing 15-SP4 base image from the bot: https://gitlab.suse.de/qac/container-release-bot/-/merge_requests/44
Updated by jlausuch about 2 years ago
Updated by jlausuch about 2 years ago
- Status changed from In Progress to Resolved
Tests are running synced with OBS-sync now: https://openqa.suse.de/group_overview/395, following same milestone build cadence as for SLES.