Project

General

Profile

Feature #8482

Feature #6196: Build all active branches

Survey usual committers about dropping the collective pseudonym for signing commits

Added by sajolida about 5 years ago. Updated over 4 years ago.

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

100%

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

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?


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 01/09/2015 07/15/2015

History

#1 Updated by sajolida about 5 years ago

  • Parent task set to #6196

#2 Updated by BitingBird about 5 years ago

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 about 5 years ago

  • 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 about 5 years ago

  • Target version set to Sustainability_M1

#5 Updated by intrigeri about 5 years ago

  • Category changed from Infrastructure to Continuous Integration

#6 Updated by intrigeri about 5 years ago

Fine with me.

#7 Updated by bertagaz about 5 years ago

  • 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 about 5 years ago

  • 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 about 5 years ago

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 about 5 years ago

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

#11 Updated by intrigeri about 5 years ago

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

#12 Updated by intrigeri about 5 years ago

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

#13 Updated by intrigeri about 5 years ago

  • 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 about 5 years ago

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

#15 Updated by intrigeri about 5 years ago

  • Assignee set to bertagaz

#16 Updated by bertagaz about 5 years ago

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

#17 Updated by bertagaz about 5 years ago

  • 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.

#19 Updated by intrigeri over 4 years ago

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

Also available in: Atom PDF