Feature #9615

Consider notifying both committer and author for development branches

Added by bertagaz 2015-06-18 11:59:11 . Updated 2017-12-16 09:50:36 .

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

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

We at first designed our Jenkins jobs to notify either the RM for main branches, or the last commiter for development branches.

It was since then raised that it might be interesting to notify both last author and commiter for development branches.

In some case it may have interesting uses, still it means quite a change to our setup. Let see if the need for it raises.


Subtasks


Related issues

Related to Tails - Feature #8655: Lead the discussion to specify what kind of branch needs to be automatically built, and when Resolved 2015-01-09 2015-06-01

History

#1 Updated by bertagaz 2015-06-18 11:59:32

#2 Updated by bertagaz 2015-06-18 11:59:57

  • related to Feature #8655: Lead the discussion to specify what kind of branch needs to be automatically built, and when added

#3 Updated by intrigeri 2015-06-19 01:42:17

Subject: Consider notifying both committer and author for development branches

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

  • Status changed from New to Confirmed

#5 Updated by intrigeri 2017-12-16 09:50:36

  • Subject changed from Consider notifying both commiter and author for development branches to Consider notifying both committer and author for development branches
  • Status changed from Confirmed to Rejected

2.5 years later, I’ve not seen us do the thing bertagaz was referring to (i.e. use the author and committer metadata Git fields cleverly), so I think we can safely reject this.