action #51041
closed[qam][feature][sprint] Release containers after successful openQA test
100%
Description
openQA tests are set up for the following continuously building repos:
SUSE:SLE-12-SP3:Docker:Update:CR
SUSE:SLE-12-SP4:Docker:Update:CR
SUSE:SLE-15:Update:CR
Soon 15-SP1 will be added.
openQA is set up, but needs to be able to release containers in case of a successful test run.
--
2020-04-09:
What we can do for a simple start is adjust that openqa does the osc release of the container.
In
mau-extratests-docker
Test-Module: /var/lib/openqa/share/tests/sle/tests/console/docker_image.pm
Either:
- If there is a RPM diff for a SLE base container, issue a "isc release ... SUSE:... " command from the openqa run itself.
(the openqa code already does container-diff --rpm)
- Or have the openqabot look at the mau-extratests-docker result and push the release in the openqabot if it has: a rpm diff and green result.
Updated by vpelcak almost 5 years ago
- Subject changed from Release containers after successful openQA test to [qam][feature] Release containers after successful openQA test
Updated by tjyrinki_suse over 4 years ago
- Priority changed from Urgent to High
Any update on status of this? Readjusting priority, if it hasn't been done by now it's probably not urgent.
Updated by cyberiad over 4 years ago
- Priority changed from High to Immediate
This was promised to Product Management to be implemented in August 2018. This even should be considered of 'Immediate' priority.
Updated by tjyrinki_suse over 4 years ago
- Assignee deleted (
hrommel1)
(was not shown in backlog since it was assigned already, to heiko)
Updated by tjyrinki_suse over 4 years ago
- Description updated (diff)
- Status changed from New to Workable
Added notes to description from the last e-mail in an e-mail thread "openQA testing SLE base containers before release". It's from Marcus Meissner, and replies to an earlier messages by Fabian Vogt and Pavel Dostal that have the following additional background:
we are currently testing the latest SLE image from internal registry, f.e.:
registry.suse.de/suse/sle-15-sp1/update/cr/images/suse/sle15But the problem is that we are still not able to match maintenance incident with particular container image.
The issue here is that the base container releasing is currently done directly
by issuing an "osc release" command. So there are no incidents or even requests
which could be matched.
This is the part where this needs discussion and coordination with maintenance
to establish a proper workflow here, which seems to be a topic for CaaSP
(and in the future also SES and others) as well.
I imagine something like this would work, similar to the openSUSE workflow:
- Release of :CR into :CR:ToTest
- Release request from :CR:ToTest into the publish location
- QA gets triggered by the release request, which tests the binars from :ToTest
- Once QA accepts the review on the release request it can be accepted
How this scales with other products (various combinations of binaries) needs
discussion.
With these and the updated description, I believe this could be set as "Workable".
Updated by geor over 4 years ago
Pavel Dostal and I are currently working on a potential solution on this, closely tied to Timo's suggestion, that will incorporate openQA as well as other components.
Updated by tjyrinki_suse about 4 years ago
- Status changed from Workable to In Progress
Updated by geor about 4 years ago
- Subject changed from [qam][feature] Release containers after successful openQA test to [qam][feature][sprint] Release containers after successful openQA test
Updated by geor about 4 years ago
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100