Feature #14611

Evaluate the global --old-iso kill switch for the test suite on Jenkins

Added by intrigeri 2017-09-07 14:28:09 . Updated 2018-06-05 15:39:14 .

Status:
Resolved
Priority:
Normal
Assignee:
intrigeri
Category:
Continuous Integration
Target version:
Tails_3.8
Start date:
2017-09-07
Due date:
% Done:

100%

Feature Branch:
Type of work:
Discuss
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

9 months after Bug #14609 and Feature #14610 are done, look back, evaluate if it’s good enough or if we need something more involved (e.g. a per-branch kill switched encoded in the branch itself).

The thing to look for is USE_LAST_RELEASE_AS_OLD_ISO in jenkins-jobs.git.

Subtasks

Related issues

Blocked by Tails - Bug #14609: Move the --old-iso kill switch from puppet-tails.git to jenkins-jobs.git Resolved 2017-09-07
Blocked by Tails - Feature #14610: Give anonym read-write access to jenkins-jobs.git Resolved 2017-09-07

History

#1 Updated by intrigeri 2017-09-07 14:28:41

  • blocked by Bug #14609: Move the --old-iso kill switch from puppet-tails.git to jenkins-jobs.git added

#2 Updated by intrigeri 2017-09-07 14:28:51

  • blocked by Feature #14610: Give anonym read-write access to jenkins-jobs.git added

#3 Updated by intrigeri 2018-06-05 15:33:46

  • Description updated

#4 Updated by intrigeri 2018-06-05 15:39:14

  • Status changed from Confirmed to Resolved
  • Target version changed from Tails_3.9 to Tails_3.8
  • % Done changed from 0 to 100

It’s been used twice only and I don’t recall cases when it hurt us to disable this globally, which suggests our current system is good enough and anything more complex would be overkill given our practical needs.

We don’t have CI team meetings anymore and some of my infrastructure work is waiting for review by my team mates since 5-10 months, so I’ll skip the discussion and review part. If anyone thinks differently, feel free to reopen and explain why :)