Project

General

Profile

Feature #9614

Automated builds: complete phase two

Added by bertagaz about 4 years ago. Updated 8 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
Continuous Integration
Target version:
-
Start date:
06/18/2015
Due date:
% Done:

78%

Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:

Description

After #5324 has been resolved and automated builds are live, we'll probably find areas that need fine tuning or polishing and new usages that might help the Tails or CI services maintenance.


Subtasks

Feature #9615: Consider notifying both committer and author for development branchesRejected

Feature #9616: Refactor Puppet bits for the nightly builds NFSConfirmedbertagaz

Feature #9719: Configure Jenkins notifications to our ticket trackerIn Progress

Feature #9741: New jobs in Jenkins should be built immediatelyRejected

Feature #9760: Prioritize builds from release branches over othersConfirmedbertagaz

Bug #10772: Next ISO builds fail on Jenkins when a previous job was aborted uncleanlyResolved

Bug #11172: Tails pythonlib is sometimes deployed with wrong permissions on jenkins.lizardRejected

Bug #11354: Disable Jenkins notifications on ISO build/test failureResolved

Feature #11355: Re-enable Jenkins notifications on ISO build/test failureIn Progress

Bug #14460: Jenkins notifications email are not sent from the correct addressResolved

Bug #12647: Deal with June 2107 false positive CI notificationsResolved

Bug #12648: Deal with July 2017 false positive CI notificationsResolved

Bug #12649: Deal with August 2017 false positive CI notificationsRejectedbertagaz

Bug #12650: Deal with September 2017 false positive CI notificationsRejectedbertagaz


Related issues

Related to Tails - Feature #5324: Automated builds: complete phase one Resolved 07/26/2013 07/15/2015

History

#1 Updated by bertagaz about 4 years ago

  • Parent task set to #6090

#2 Updated by bertagaz about 4 years ago

  • Related to Feature #7107: Refactor Puppet code for Jenkins from www.lizard added

#3 Updated by bertagaz about 4 years ago

  • Related to deleted (Feature #7107: Refactor Puppet code for Jenkins from www.lizard)

#4 Updated by intrigeri about 4 years ago

  • Description updated (diff)

#5 Updated by intrigeri about 4 years ago

  • Parent task deleted (#6090)

Dropping the parent task, otherwise we won't close #6090 ever.

#6 Updated by intrigeri about 4 years ago

  • Related to Feature #5324: Automated builds: complete phase one added

#7 Updated by BitingBird about 3 years ago

  • Status changed from Confirmed to In Progress

#8 Updated by u about 2 years ago

  • Assignee set to bertagaz

Simply assigning the parent ticket to bertagaz for tracking as all subtickets currently belong to you.

#9 Updated by intrigeri 8 months ago

IMO this parent tracking ticket is not useful anymore:

  • These days, CI issues are simply being reported under the "Continuous Integration" category, so there's a way to find them.
  • If we took a step back and updated our current CI priorities, I bet we would realize that this ticket and its subtasks don't reflect them at all. In this sense, this ticket is useless and IMO even misleading.

So I recommend unparenting the subtasks and rejecting this one.

#10 Updated by bertagaz 8 months ago

intrigeri wrote:

So I recommend unparenting the subtasks and rejecting this one.

Or make this other tickets children of this one? I think the goal of this ticket was to also try to have a vision of what we think could be the next step in the development of our CI (including thinking what we could gather for a grant submission), so it might makes sense to have a parent ticket to track them, rather than a list of tickets.

#11 Updated by intrigeri 8 months ago

Or make this other tickets children of this one?

This won't solve any problem I personally experience or foresee, but I understand it will help you, so: fine by me!

Also available in: Atom PDF