Project

General

Profile

Feature #8072

Set up a second Jenkins slave to build ISO images

Added by intrigeri about 5 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Continuous Integration
Target version:
-
Start date:
10/11/2014
Due date:
% Done:

100%

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

Description

Quite often, ISO builds triggered by Jenkins are queuing up. Let's add a 2nd ISO builder, and allocate 6 vcpus to each builder. (Probably remove one of the debomatic's vCPUs along the way.)


Related issues

Related to Tails - Bug #10999: Parallelize our ISO building workload on more builders Resolved 01/26/2016
Blocks Tails - Feature #6196: Build all active branches Resolved 08/07/2013 07/15/2015

History

#1 Updated by intrigeri almost 5 years ago

  • Related to Feature #7106: Refactor Puppet code for the Jenkins slave on builder.lizard added

#2 Updated by intrigeri almost 5 years ago

  • Related to deleted (Feature #7106: Refactor Puppet code for the Jenkins slave on builder.lizard)

#3 Updated by intrigeri almost 5 years ago

  • Blocked by Feature #7106: Refactor Puppet code for the Jenkins slave on builder.lizard added

#4 Updated by intrigeri almost 5 years ago

I've had a look, and this would simply be too ugly to do before #7106 is fixed.

#5 Updated by intrigeri almost 5 years ago

  • Blocked by deleted (Feature #7106: Refactor Puppet code for the Jenkins slave on builder.lizard)

#6 Updated by intrigeri almost 5 years ago

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10

#8 Updated by intrigeri almost 5 years ago

#9 Updated by intrigeri almost 5 years ago

  • Target version set to Sustainability_M1

Blocks a 2.0 goal, hence flagging for 2.0 too.

#10 Updated by bertagaz almost 5 years ago

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)

Meet 'isobuilder2', carbon copy of 'builder' (who has been renamed to 'isobuilder1').

Been created and put in production yesterday. Hopefully it will help for future drafts of our infrastructure hardware, but so far no big news, each new isobuilder mostly consume CPU time.

#11 Updated by bertagaz almost 5 years ago

  • % Done changed from 10 to 100

#12 Updated by sajolida about 4 years ago

  • Target version deleted (Sustainability_M1)

#13 Updated by intrigeri over 3 years ago

  • Related to Bug #10999: Parallelize our ISO building workload on more builders added

Also available in: Atom PDF