action #13780
closed
[tools][dashboard]Level of importance of test_suites + architectures
Added by okurz over 7 years ago.
Updated over 6 years ago.
Category:
Feature requests
Description
user stories¶
- As a reviewer I want to know which test suites / scenarios / architectures are more important than others to review the important ones first
- As a release manager I want important jobs to be triggered first so that I get faster feedback on these
acceptance criteria¶
- AC1: A reviewer can see within openQA on the overview page which jobs belong to more important test_suites / scenarios / architectures
- AC2: Important jobs are scheduled with higher priority than less important ones and therefore are triggered first
further details¶
Proposed by ast
the scheduling is done by priority. And I don't think we should split job groups even further.
the scheduling is done by priority
I know, that is why we can rely on this feature and set an even more fine grained priority for jobs within a job group.
And I don't think we should split job groups even further
I agree. I didn't think otherwise and didn't mention job groups.
but that's what you're doing. You split SP2 Server jobs into 7 job groups - and within that group create important and non-important jobs (whereever that line should be drawn). I'd say: no
As stated, the original idea was by ast. IMHO it's still a good idea. I would not mind to discuss that in person. In the end, the test_suites already have a relative priority, it's just not shown in openQA but maybe only in some spreadsheet of RM/PM or the head of the reviewers. IMHO different levels of importance would allow to scale more, maybe even allow to merge together multiple job groups again.
- Category set to Feature requests
- Subject changed from Level of importance of test_suites + architectures to [tools][dashboard]Level of importance of test_suites + architectures
- Status changed from New to Rejected
I didn't buy the argument then and I don't buy it now.
Also available in: Atom
PDF