Feature #5558

Build an ISO on Git push

Added by Tails 2013-07-18 07:42:46 . Updated 2014-08-02 16:36:54 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Continuous Integration
Target version:
Sustainability_M1
Start date:
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

Have the master repository on immerda push to gitolitepuppet-git.lizard:tails@, e.g. using Gitolite’s mirroring support or a simple post-receive hook.

Subtasks

History

#1 Updated by Tails 2013-07-18 10:36:33

#2 Updated by bertagaz 2013-07-26 14:13:10

  • Starter set to No

There should be a wait before really starting the build after this kind of trigger, in case another HEAD is pushed soon after. This would prevent ending up with too many builds in the queue.

Not sure how easy it is to implement on the git{,olite} side though. Might be easier in jenkins, but this need some research

#3 Updated by intrigeri 2013-07-27 01:42:18

> There should be a wait before really starting the build after this kind of trigger,
> in case another HEAD is pushed soon after. This would prevent ending up with too many
> builds in the queue.

It’s unclear to me what problem this would solve. Do you mean a more
recent version of the same branch being pushed soon after, or another
branch being pushed soon after?

(To be honest, this looks a bit like premature optimization to me.
I’d rather do the simplest thing that can possibly work and be useful
first, and then detect bottlenecks if any, and then only fix them.)

#4 Updated by intrigeri 2013-12-29 04:01:19

  • Subject changed from build an ISO on Git push to Build an ISO on Git push

#5 Updated by intrigeri 2014-08-02 16:36:54

  • Status changed from Confirmed to Resolved
  • % Done changed from 0 to 100

This was implemented a few days ago.