Project

General

Profile

Actions
Copy link

action #13780

closed

[tools][dashboard]Level of importance of test_suites + architectures

Added by okurz about 8 years ago. Updated about 7 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
-
Start date:
2016-09-16
Due date:
% Done:

0%

Estimated time:

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

Actions
Copy link
 #1

Updated by coolo about 8 years ago

the scheduling is done by priority. And I don't think we should split job groups even further.

Actions
Copy link
 #2

Updated by okurz about 8 years ago

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.

Actions
Copy link
 #3

Updated by coolo about 8 years ago

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

Actions
Copy link
 #4

Updated by okurz about 8 years ago

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.

Actions
Copy link
 #5

Updated by okurz almost 8 years ago

  • Category set to Feature requests
Actions
Copy link
 #6

Updated by RBrownSUSE over 7 years ago

  • Subject changed from Level of importance of test_suites + architectures to [tools][dashboard]Level of importance of test_suites + architectures
Actions
Copy link
 #7

Updated by coolo about 7 years ago

  • Status changed from New to Rejected

I didn't buy the argument then and I don't buy it now.

Actions
Copy link

Also available in: Atom PDF