action #113036
Updated by jlausuch almost 2 years ago
From Jiri Srain: > Jiri, another thing ... should opensuse-toolbox-image be part of a QA pipeline? So far we are not updating it and it can get security issues? That is actually a good point - yes, we should IMO update it (for released versions of SLE Micro) on regular basis. This would be: SUSE:SLE-15-SP3:Update:Products:MicroOS51:Update:CR opensuse-toolbox-image SUSE:SLE-15-SP3:Update:Products:MicroOS51:Update:CR:ToTest opensuse-toolbox-image SUSE:SLE-15-SP3:Update:Products:MicroOS52:Update:CR opensuse-toolbox-image SUSE:SLE-15-SP3:Update:Products:MicroOS52:Update:CR:ToTest opensuse-toolbox-image And when SLE Micro 5.3 is released: SUSE:SLE-15-SP4:Update:Products:Micro53:Update:CR opensuse-toolbox-image SUSE:SLE-15-SP4:Update:Products:Micro53:Update:CR:ToTest opensuse-toolbox-image ### Test Matrix: Each toolbox image shall To be tested on the respective SLE Micro host. For example, for Toolbox 5.1: - Boot SLE Micro 5.1 GA image - Perform a system update - Run tests for Toolbox image under test described. ## Acceptance Criteria - Write a simple test case `test_toolbox.py` in [BCI-tests repo](https://github.com/SUSE/BCI-tests) - Create a new job group in openQA called Toolbox under [Containers parent group](https://openqa.suse.de/parent_group_overview/35#grouped_by_build) which contains needed hosts from the matrix. - Enable the container in the [container release bot](https://gitlab.suse.de/qac/container-release-bot/-/tree/main/containers) - Have green tests in openQA