Feature #9614

Automated builds: complete phase two

Added by bertagaz 2015-06-18 11:47:35 . Updated 2018-12-03 20:43:16 .

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

78%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

After Feature #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 branches Rejected

0
Feature #9616: Refactor Puppet bits for the nightly builds NFS Confirmed bertagaz

0
Feature #9719: Configure Jenkins notifications to our ticket tracker Confirmed

10
Feature #9741: New jobs in Jenkins should be built immediately Rejected

0
Feature #9760: Prioritize builds from release branches over others Confirmed bertagaz

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

100
Bug #11172: Tails pythonlib is sometimes deployed with wrong permissions on jenkins.lizard Rejected

100
Bug #11354: Disable Jenkins notifications on ISO build/test failure Resolved

100
Feature #11355: Re-enable Jenkins notifications on ISO build/test failure In Progress

100
Bug #12647: Deal with June 2107 false positive CI notifications Resolved

100
Bug #12648: Deal with July 2017 false positive CI notifications Resolved

100
Bug #12649: Deal with August 2017 false positive CI notifications Rejected bertagaz

0
Bug #12650: Deal with September 2017 false positive CI notifications Rejected bertagaz

0

Related issues

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

History

#1 Updated by bertagaz 2015-06-18 11:48:05

#2 Updated by bertagaz 2015-06-18 13:07:35

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

#3 Updated by bertagaz 2015-06-18 13:07:44

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

#4 Updated by intrigeri 2015-06-19 01:44:05

  • Description updated

#5 Updated by intrigeri 2015-06-19 01:45:22

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

#6 Updated by intrigeri 2015-06-19 01:46:28

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

#7 Updated by BitingBird 2016-06-26 08:25:34

  • Status changed from Confirmed to In Progress

#8 Updated by Anonymous 2017-06-28 14:20:39

  • Assignee set to bertagaz

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

#9 Updated by intrigeri 2018-12-02 17:58:59

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 2018-12-03 20:21:07

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 2018-12-03 20:43:16

> 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!