Feature #10287
Set up limited email notification on automatic test failure for the initial deployment
100%
Description
On 2015-10-15 (latest) our jenkins test suite deployment should have happened.
To prevent an avalanche of failure notifications that may scare contributors away, let’s limit the receivers to the test suite team (anonym and kytv) for the first week, and then reevaluate if we can carry out the intended plan of notifying the last author of each failing branch.
Subtasks
Related issues
Related to Tails - Bug #10288: Fix newly identified issues to make our test suite more robust and faster | In Progress | 2015-02-26 | |
Blocks Tails - |
Resolved | 2015-09-28 | |
Blocked by Tails - |
Resolved | 2015-08-28 |
History
#1 Updated by anonym 2015-09-27 06:13:53
- Tracker changed from Bug to Feature
- Parent task set to
Feature #5288
#2 Updated by intrigeri 2015-09-28 02:06:34
- Subject changed from Plan for test suite failure notifications during initial jenkins deployment to Plan for test suite failure notifications during initial Jenkins deployment
- Category changed from Infrastructure to Continuous Integration
- Target version set to Tails_1.7
- Type of work changed from Code to Sysadmin
- Deliverable for set to 267
#3 Updated by intrigeri 2015-09-28 02:06:43
- blocks #8668 added
#4 Updated by bertagaz 2015-09-28 03:51:03
- Subject changed from Plan for test suite failure notifications during initial Jenkins deployment to Set up email notification as planned for the initial deployment
- Description updated
#5 Updated by bertagaz 2015-09-28 03:59:22
- blocks
Feature #10296: Reevaluate how the email notifications for failed automatic tests scale added
#6 Updated by anonym 2015-09-28 04:52:13
- related to Bug #10288: Fix newly identified issues to make our test suite more robust and faster added
#7 Updated by sajolida 2015-10-01 07:27:10
- Priority changed from Normal to Elevated
Note that this is due on October 15 which is actually before Tails 1.7. Raising priority accordingly.
#8 Updated by intrigeri 2015-10-03 15:06:51
- Subject changed from Set up email notification as planned for the initial deployment to Set up limited email notification on automatic test failure for the initial deployment
#9 Updated by bertagaz 2015-10-13 12:05:44
- 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
- Starter set to No
The feature/10287-limited-email-notifications
of the jenkins-jobs
Git repo contains an additional commit to the feature/10119-adapt-job-generation-script
which enables email notifications for the test jobs.
With just this commit, the test jobs would send their notifications to the same recipients than for their upstream build jobs.
With the commit in the feature/10287-limited-email-notifications
branch of the puppet-tails
repo, the generated jenkins-job-builder project definition of an active branch is configured to send an email notification as usual for the build jobs, and send the notifications of all test jobs to the testing team mates, implementing this ticket.
We should probably merge this a bit later than the feature/10119-adapt-job-generation-script
branch, when the Feature #6094 cabal is over.
#10 Updated by intrigeri 2015-10-14 00:00:30
- Assignee changed from intrigeri to bertagaz
- QA Check changed from Ready for QA to Dev Needed
Reviewed, looks good! and then:
> We should probably merge this a bit later than the feature/10119-adapt-job-generation-script
branch, when the Feature #6094 cabal is over.
OK, then please deploy once sensible.
#11 Updated by intrigeri 2015-10-14 00:01:12
- blocked by
Feature #10119: Adapt the job generation script to also output corresponding test jobs added
#12 Updated by intrigeri 2015-10-14 00:01:31
- blocked by
Feature #6094: Test suite: background snapshot improvements added
#13 Updated by bertagaz 2015-10-19 03:45:50
- blocks deleted (
)Feature #6094: Test suite: background snapshot improvements
#14 Updated by bertagaz 2015-10-19 03:48:10
- Status changed from In Progress to Resolved
- Assignee deleted (
bertagaz) - % Done changed from 80 to 100
- QA Check deleted (
Dev Needed)
It’s been merged yesterday, with a small patch to filter out branches that are too old regarding the build and test components (mainly the one based on stable, which are doc/ and web/ branches).
#15 Updated by intrigeri 2015-10-23 07:34:07
Yay! :)