Feature #8482

Survey usual committers about dropping the collective pseudonym for signing commits

Added by sajolida 2014-12-23 16:30:01 . Updated 2015-08-26 06:09:04 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Continuous Integration
Target version:
Tails_1.3
Start date:
2014-12-23
Due date:
2015-01-30
% Done:

100%

Feature Branch:
Type of work:
Communicate
Blueprint:

Starter:
Affected tool:
Deliverable for:
266

Description

If we want Jenkins to send notification related to automated build and tests to the person who is working on the corresponding branch, then those commits should be identified somehow, which cannot be the case as long as we all use the ‘Tails developers’ name.

See https://mailman.boum.org/pipermail/tails-dev/2014-December/007578.html

How would people feel about that?

Subtasks

Related issues

Related to Tails - Feature #8656: Write code that generates a set of Jenkins jobs for all branches we want to automatically build Resolved 2015-01-09 2015-07-15

History

#1 Updated by sajolida 2014-12-23 16:31:59

#2 Updated by BitingBird 2014-12-24 02:06:01

I don’t really care one way or another. Whatever is more practical and/or safe for others is fine by me.

#3 Updated by intrigeri 2014-12-24 12:01:23

  • Subject changed from Survey usual committers about drop the collective pseudonym for signing commits to Survey usual committers about dropping the collective pseudonym for signing commits

#4 Updated by intrigeri 2014-12-24 12:01:57

  • Target version set to Sustainability_M1

#5 Updated by intrigeri 2014-12-24 12:02:28

  • Category changed from Infrastructure to Continuous Integration

#6 Updated by intrigeri 2014-12-24 12:04:13

Fine with me.

#7 Updated by bertagaz 2014-12-25 12:45:52

  • Category changed from Continuous Integration to Infrastructure
  • Target version deleted (Sustainability_M1)

I’m fine with it.

That said, I see another implementation: we could have jenkins send emails to our redmine, to the ticket assigned to the branch being build.

That way, jenkins notifications aren’t bound on the commit author, but on people watching the corresponding ticket.

#8 Updated by intrigeri 2014-12-25 13:27:37

  • Category changed from Infrastructure to Continuous Integration
  • Target version set to Sustainability_M1

(Setting ticket metadata to the same as the parent ticket, again.)

#9 Updated by sajolida 2014-12-25 13:30:11

I’m ok with signing my commits as sajolida.

I also like the new idea of bertagaz as this would make the debugging information public instead of private.

The downside is that we would have to be stricter about associating branches with tickets (and what happen when this is not a one-to-one relationship?).

#10 Updated by intrigeri 2015-01-04 12:41:03

  • blocks Feature #6216: Email notification on failed Jenkins build added

#11 Updated by intrigeri 2015-01-09 17:49:12

  • blocks Feature #8658: Deploy the "build all active branches" system added

#12 Updated by intrigeri 2015-01-09 17:49:18

  • blocked by deleted (Feature #8658: Deploy the "build all active branches" system)

#13 Updated by intrigeri 2015-01-09 17:49:28

  • related to Feature #8656: Write code that generates a set of Jenkins jobs for all branches we want to automatically build added

#14 Updated by intrigeri 2015-01-09 17:49:46

  • Target version changed from Sustainability_M1 to Tails_1.4
  • Type of work changed from Discuss to Communicate

#15 Updated by intrigeri 2015-01-09 17:51:26

  • Assignee set to bertagaz

#16 Updated by bertagaz 2015-01-10 05:39:30

  • Due date set to 2015-01-30
  • Target version changed from Tails_1.4 to Tails_1.3

#17 Updated by bertagaz 2015-01-13 18:30:52

  • Status changed from Confirmed to Resolved
  • Assignee deleted (bertagaz)
  • % Done changed from 0 to 100

Every “usual commiters” replied positively to this survey, so I’m closing the ticket.

#18 Updated by intrigeri 2015-05-29 11:36:21

  • blocks #8668 added

#19 Updated by intrigeri 2015-05-31 13:57:14

  • blocked by deleted (Feature #6216: Email notification on failed Jenkins build)

#20 Updated by intrigeri 2015-08-26 06:09:04

  • Deliverable for set to 266