Project

General

Profile

Feature #12505

Feature #5630: Reproducible builds

Switch isobuilders to vagrant-libvirt in Puppet

Added by bertagaz 6 months ago. Updated 21 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
05/03/2017
Due date:
% Done:

0%

QA Check:
Dev Needed
Feature Branch:
puppet-tails:feature/11972-use-vagrant-in-jenkins
Type of work:
Sysadmin
Blueprint:
Easy:
Affected tool:

Description

This ticket is meant to track the puppet part of the implementation of vagrant-libvirt on our Jenkins isobuilders. The tails.git part has been achieved in #11972. #11972#note-5 and following notes contain some initial review from intrigeri, that needs to be addressed. The complete switch in puppet also needs to be finished in a dedicated branch of puppet-tails.

History

#1 Updated by bertagaz 6 months ago

  • Related to Feature #11972: Switch our Jenkins ISO build system to vagrant-libvirt added

#2 Updated by bertagaz 6 months ago

  • Assignee changed from bertagaz to intrigeri
  • QA Check changed from Dev Needed to Info Needed

I think all remarks made in the initial review (#11972#note-5 to #11972#note-13) has been addressed.

All the Puppet code is also already written in the feature branch, as the plan is to re-install all Jenkins isobuilders to stretch one by one, each time setting them to tails::jenkins::slave::iso_builder::use_vagrant: true in hiera so that they switch to vagrant based builds.
Once they all have migrated, the use_vagrant condition in ::tails::jenkins::slave::iso_builder will be removed, as well as any traces of ::tails::builder.

Does this make sense?

One black hole in this is how to manage the sib isobuilder. What's your plan regarding this?

#3 Updated by intrigeri 6 months ago

Don't wait for me before you start implementing everything you want in a Puppet Git branch, otherwise everything will be delayed by possibly 1 week.

#4 Updated by intrigeri 6 months ago

  • Assignee changed from intrigeri to bertagaz
  • QA Check changed from Info Needed to Dev Needed

(As explained above, don't block on me at a time when I've announced I would be unavailable: go ahead and I'll review your stuff either in Git or once deployed.)

#5 Updated by intrigeri 5 months ago

bertagaz wrote:

Once they all have migrated, the use_vagrant condition in ::tails::jenkins::slave::iso_builder will be removed, as well as any traces of ::tails::builder.

Does this make sense?

Yes => please prepare this in a (preferably tested) branch and submit it for review.

One black hole in this is how to manage the sib isobuilder. What's your plan regarding this?

Just let me know what manual migration steps I have to do, on top of what Puppet does.

#6 Updated by bertagaz 5 months ago

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

#7 Updated by intrigeri 5 months ago

  • Target version changed from Tails_3.0 to Tails_3.1

Please focus on actual breakage for now, this refactoring can wait a bit :)

#8 Updated by intrigeri 4 months ago

  • Priority changed from Elevated to Normal

#9 Updated by intrigeri 4 months ago

  • Related to deleted (Feature #11972: Switch our Jenkins ISO build system to vagrant-libvirt)

#10 Updated by intrigeri 4 months ago

  • Parent task set to #5630

#11 Updated by intrigeri 4 months ago

  • Target version changed from Tails_3.1 to Tails_3.2

intrigeri wrote:

Please focus on actual breakage for now, this refactoring can wait a bit :)

Same :)

#13 Updated by anonym 21 days ago

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

Also available in: Atom PDF