Bug #11006

Reinstall Lizard's isobuilders from scratch

Added by bertagaz 2016-01-27 13:01:50 . Updated 2017-05-16 07:28:04 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Continuous Integration
Target version:
Start date:
2016-01-27
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
0
Affected tool:
Deliverable for:
289

Description

As noted in Bug #10772#note-8, our isobuilders have slight differences that may explain why we see sometimes different behaviors. When we’ll port our build system to Jessie, we then should reinstall then from scratch rather than simply upgrade them, to get a more deterministic behavior.


Subtasks


Related issues

Blocked by Tails - Bug #9262: Port our ISO build system to Jessie Resolved 2015-04-19

History

#1 Updated by bertagaz 2016-01-27 13:02:20

  • blocked by Bug #9262: Port our ISO build system to Jessie added

#2 Updated by bertagaz 2016-01-27 13:02:33

  • related to Bug #10772: Next ISO builds fail on Jenkins when a previous job was aborted uncleanly added

#3 Updated by intrigeri 2016-02-12 23:56:41

  • Target version changed from Tails_2.2 to Tails_2.3

(Blocked by something that’s blocked by something that will be done very late in the 2.2 cycle, if I’m lucky.)

#4 Updated by intrigeri 2016-02-27 10:29:57

  • related to deleted (Bug #10772: Next ISO builds fail on Jenkins when a previous job was aborted uncleanly)

#5 Updated by bertagaz 2016-04-26 05:00:07

  • Target version changed from Tails_2.3 to Tails_2.4

#6 Updated by bertagaz 2016-06-07 12:31:36

  • Target version changed from Tails_2.4 to Tails_2.5

#7 Updated by bertagaz 2016-07-19 04:17:25

  • Target version changed from Tails_2.5 to Tails_2.6

#8 Updated by anonym 2016-09-20 16:54:04

  • Target version changed from Tails_2.6 to Tails_2.7

#9 Updated by bertagaz 2016-09-22 05:37:35

  • Target version changed from Tails_2.7 to Tails_2.9.1

#10 Updated by anonym 2016-12-14 20:11:22

  • Target version changed from Tails_2.9.1 to Tails 2.10

#11 Updated by intrigeri 2017-01-11 07:43:49

  • Target version changed from Tails 2.10 to Tails_2.12

#12 Updated by bertagaz 2017-04-06 14:27:28

  • Target version changed from Tails_2.12 to Tails_3.0

#13 Updated by intrigeri 2017-04-16 10:36:34

I’ve upgraded isobuilder1.sib to Stretch, adjusted our Puppet code to support this, and adjusted our build system (commit:48498f40a9263fe068279f084c4e541cfee684e3). So please install Stretch on them so we don’t have to go through upgrades :)

#14 Updated by intrigeri 2017-04-18 15:15:51

  • Target version changed from Tails_3.0 to Tails_3.0~rc1

Same as Feature #11972#note-26.

#15 Updated by bertagaz 2017-05-07 11:35:57

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

I’m reinstalling the isobuilders with Feature #11972 since yesterday. isobuilder3 and isobuilder4 are done, doing isobuilder2 right now. Then I’ll merge the Feature #11972 branch.

#16 Updated by bertagaz 2017-05-09 13:57:58

  • Status changed from In Progress to Fix committed
  • % Done changed from 50 to 100

Applied in changeset commit:79b7f9ca5f09584bcaa4d948bff56ca2d9ffa30a.

#17 Updated by bertagaz 2017-05-12 09:33:22

  • Status changed from Fix committed to In Progress
  • Assignee changed from bertagaz to intrigeri
  • % Done changed from 100 to 80
  • QA Check changed from Dev Needed to Ready for QA

I’ve reinstalled all isobuilders with the same setup than what have been done on isobuilder1.lizard (which also means upgrading to Stretch). I’ve also unified the puppet manifests in our main Puppet repo (modules/local/manifests/node/isobuilder.pp), and updated the install notes in the sysadmins Git repo. Please have a look and close this ticket if happy. I’ll tackle the remaining Puppet stuffs in Feature #12505.

#18 Updated by intrigeri 2017-05-16 07:28:04

  • Status changed from In Progress to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 80 to 100
  • QA Check changed from Ready for QA to Pass
  • Deliverable for set to 289

Looks great! I’ll keep filing tickets for every resulting breakage or misbehavior I notice :)