Project

General

Profile

action #11072

Always finish important builds

Added by okurz about 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
-
Start date:
2015-11-13
Due date:
% Done:

0%

Estimated time:
Difficulty:
Duration:

Description

user stories

  • As a QA SLE product manager I want important builds to finish even if new (non-important) builds come in to have complete results for important builds

acceptance criteria

  • All tests in an important build are not aborted if a new build is triggered
  • Non-important builds may still be aborted

tasks

  1. important builds are not aborted on new builds
    • Given important build exists (see #9544)
    • When new build is triggered
    • Then no test of the important build is obsoleted

Related issues

Blocks openQA Project - action #9760: "Finish Testing a Build" (aka Un-Obsolete) and "Retest entire build"Resolved2015-12-01

Copied from openQA Project - action #9544: Build TaggingResolved2015-11-13

History

#1 Updated by okurz about 4 years ago

#2 Updated by okurz almost 4 years ago

  • Blocks action #9760: "Finish Testing a Build" (aka Un-Obsolete) and "Retest entire build" added

#3 Updated by okurz almost 4 years ago

  • Assignee set to okurz

#4 Updated by okurz almost 4 years ago

  • Status changed from New to In Progress

#5 Updated by okurz almost 4 years ago

  • Status changed from In Progress to Feedback

feature merged and deployed, waiting for feedback if it works or if there are problems with this.

#6 Updated by okurz almost 4 years ago

  • Status changed from Feedback to Resolved

hm, nobody complained but there were no new builds which would obsolete old ones. Let's take this as done, then.

Also available in: Atom PDF