action #58268
closed[kernel][public cloud] Fix OpenQA view with different versions of different flavors
0%
Description
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)
...
Updated by asmorodskyi about 5 years ago
- Description updated (diff)
- Status changed from Workable to In Progress
- Assignee set to asmorodskyi
there is 3d option : keep current build numbering but just split builds into 3 different sub-groups so you will not have problems with ordering and you will not have problems with search for some certain build .
About first two solutions - as I understand from what Robert was saying SLES builds numbering is hard to map to PC world . Sometimes PC can ship several builds during same SLES build . Also we will start to get difficulties in discussions with PC developers . They have no idea what is 0358 means , they know meaning of 0.9.1-1.44 . So I am strongly against using SLES build numbers in PC world
Updated by asmorodskyi about 5 years ago
- Status changed from In Progress to Feedback
- Assignee deleted (
asmorodskyi)
So after discussion with Jose and Clemens - 3d option was accepted by everyone. I create 3 sub-group under "SLE 12 SP5 Public Cloud " and did the same under "SLE 15 SP2 Public Cloud" . each sub-group will handle only build for certain PCP . As mentioned by Clemens we still can have some "mess" inside each PCP , because there is a lot of cases when each PCP has different build for BYOS and OnDemand images but was decided to keep it like this for some time to see what advantages / disadvantages current model has so we can more clear decide what to do as next step
Updated by jlausuch about 5 years ago
Yes, I noticed that behaviour in the different sub-groups, but it looks much better than before. At least, it's much faster to look for tests of specific Cloud Provider, and it will be easy to integrate Oracle in the future and not mess up the view.
Thanks! Feel free to mark it as Resolved.
Updated by asmorodskyi about 5 years ago
- Status changed from Feedback to Resolved
Updated by cfconrad about 5 years ago
- Related to action #58739: [qac][jdp][public cloud] Group publiccloud images by FLAVOR in JDP report added
Updated by pcervinka about 4 years ago
- Target version changed from 457 to QE Kernel Done