Bug #11354

Disable Jenkins notifications on ISO build/test failure

Added by intrigeri 2016-04-15 06:36:28 . Updated 2016-04-25 02:46:01 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Continuous Integration
Target version:
Tails_2.3
Start date:
2016-04-15
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:
280

Description

Our contributors survey shows that they are currently mostly indistiguishible from spam. Let’s disable them ASAP, and then we can re-enable them one by one, carefully evaluating the outcome at each step.

Subtasks

Related issues

Blocks Tails - Feature #11355: Re-enable Jenkins notifications on ISO build/test failure In Progress 2017-08-28

History

#1 Updated by intrigeri 2016-04-15 06:39:04

For base branches, we still want to notify the RMs.

#2 Updated by intrigeri 2016-04-15 06:40:57

  • blocks Feature #11355: Re-enable Jenkins notifications on ISO build/test failure added

#3 Updated by intrigeri 2016-04-15 06:47:24

#4 Updated by intrigeri 2016-04-15 06:48:20

  • blocked by deleted (Feature #11355: Re-enable Jenkins notifications on ISO build/test failure)

#5 Updated by intrigeri 2016-04-15 06:48:55

  • blocks Feature #11355: Re-enable Jenkins notifications on ISO build/test failure added

#6 Updated by bertagaz 2016-04-22 07:44:17

  • Status changed from Confirmed to In Progress
  • Assignee changed from bertagaz to intrigeri
  • % Done changed from 0 to 80
  • QA Check set to Ready for QA

Implemented the simpler way in commit puppet-tails:99bacf2. A more elaborated implementation will be needed when tackling Feature #11355, which won’t be easy given how we abstracted our job generation in JJB code.

#7 Updated by bertagaz 2016-04-22 07:51:46

First run in Jenkins after the change confirms no email are sent for dev branches anymore: https://jenkins.tails.boum.org/job/build_Tails_ISO_doc-11025-browser-fingerprint/38/console

#8 Updated by intrigeri 2016-04-25 02:42:33

  • Status changed from In Progress to Resolved
  • % Done changed from 80 to 100
  • QA Check changed from Ready for QA to Pass

> Implemented the simpler way in commit puppet-tails:99bacf2.

Looks good enough, and my inbox confirms that it works.

> A more elaborated implementation will be needed when tackling Feature #11355, which won’t be easy given how we abstracted our job generation in JJB code.

I’ve no idea what you mean with “won’t be easy given […]”, but I guess I’ll understand better once you actually tackle it :)

#9 Updated by intrigeri 2016-04-25 02:46:01

  • Assignee deleted (intrigeri)