Feature #12391

Run full test suite when building from a release tag

Added by anonym 11 months ago. Updated about 1 month ago.

Continuous Integration
Target version:
Start date:
Due date:
% Done:


QA Check:
Info Needed
Feature Branch:
Type of work:
Affected tool:


When jenkins notices a tag has been pushed or modified (from git push -f --tags) it should check if the changelog at the tagged commit has its first entry != UNRELEASED. Then we know that that is a commit/tag the we are releasing, so it should add a build from that exact tag. And in the test suite it should run all tests (i.e. drop do not do --tag ~@fragile).

This will be a step towards involving Jenkins in our release process for real, and the full test suite run will gather some interesting data about how well the @fragile tagged tests are running on Jenkins. We could save these (ideally Jenkins should be told to keep builds of release tags longer than other builds) and look at them once or twice a year to see if it seems some tests are not fragile on Jenkins any more.


#1 Updated by anonym 11 months ago

  • Description updated (diff)

#2 Updated by anonym 11 months ago

  • Assignee set to bertagaz

What do you think? :)

#3 Updated by u 8 months ago

ping @bertagaz :)

#4 Updated by intrigeri 8 months ago

  • Status changed from New to Confirmed
  • QA Check set to Info Needed

#5 Updated by intrigeri 7 months ago

  • Target version set to Tails_3.2

#6 Updated by intrigeri 7 months ago

(Just so the initial question is on bertagaz' radar. The goal is not to implement this for 3.2.)

#7 Updated by bertagaz 5 months ago

  • Target version changed from Tails_3.2 to Tails_3.3

#8 Updated by bertagaz 4 months ago

  • Target version changed from Tails_3.3 to Tails_3.5

Realistically reschedule for 3.4.

#9 Updated by u about 1 month ago

  • Target version changed from Tails_3.5 to Tails_3.6

Postpone this again.

Also available in: Atom PDF