action #58268
Updated by asmorodskyi over 4 years ago
Currently, we are grouping Public Cloud tests depending on the Cloud Build and the Kiwi Build, which are most of the same different for different providers. This makes the grouping of the tests cases a bit tricky, always depending on those build numbers. This has some drawbacks (e.g. searching specific tests, JDP, ...) and makes the view very complex.
The idea is to come up with a solution to group the tests in a smarter way. From the ISOS POST, we could change the BUILD variable we pass to OpenQA.
2 ways:
1) Use same BUILD number as the corresponding SLES build to the PC images
Advantage: everything is in the same place, we can even merge the group with SLE1X job groups
It would look something like this:
Build0358 (a day ago)
Build0357 (4 days ago)
Build0350 (8 days ago)
Build0346 (8 days ago)
2) Group them by SLES build number and also by Provider name:
Advantage: easy to find tests for specific provider
Disadvantage: we can't merge it in the SLE1X groups, we would need to keep it in Public Cloud group.
IT would look something like this:
Build0358-Azure (a day ago)
Build0358-EC2 (a day ago)
Build0358-GCE (a day ago)
Build0357-Azure (a day ago)
Build0357-EC2 (a day ago)
Build0357-GCE (a day ago)
...
In both cases, the associated SLES build can be taken from the ISOS directory:
http://dist.suse.de/ibs/SUSE:/SLE-12-SP5:/GA:/TEST/images/iso/
For example, looking at the ISO with the name SLE-12-SP5-Server-DVD-x86_64-Build0358-Media1.iso
we can say that the generated public cloud builds are the corresponding in http://dist.suse.de/ibs/SUSE:/SLE-12-SP5:/GA:/TEST/images