Bug #12681

reproducibly_build_Tails_ISO_* Jenkins jobs are buggy when building from a tag

Added by intrigeri 2017-06-10 14:54:58 . Updated 2017-10-19 13:56:55 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Continuous Integration
Target version:
Start date:
2017-06-10
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:
301

Description

We get two ISOs called exactly the same, so the 2nd one overwrites the 1st one and there’s nothing to compare. E.g. https://jenkins.tails.boum.org/job/reproducibly_build_Tails_ISO_testing/46/console.

Too bad, release time is perhaps one of the times when those results are most useful.

This should be trivial to fix while working on Feature #12633.


Subtasks


History

#1 Updated by intrigeri 2017-06-22 13:50:07

  • Deliverable for set to 289

#2 Updated by intrigeri 2017-07-18 12:22:07

  • Deliverable for changed from 289 to 301

#3 Updated by intrigeri 2017-09-05 06:31:34

  • Status changed from Confirmed to In Progress
  • Assignee changed from intrigeri to bertagaz
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA

Seems to work: https://jenkins.tails.boum.org/view/RM/job/reproducibly_build_Tails_ISO_devel/50/console and https://jenkins.tails.boum.org/view/RM/job/reproducibly_build_Tails_ISO_devel/50/artifact/build-artifacts/. Corresponding commits in puppet-tails and jenkins-jobs repos are flagged with this ticket ID.

#4 Updated by intrigeri 2017-09-05 06:32:32

Also, note that this is the cheap, short term workaround, that will be obsoleted by the implementation I have in mind for Feature #12633.

#6 Updated by anonym 2017-09-28 18:29:19

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

#7 Updated by bertagaz 2017-10-19 13:56:55

  • Status changed from In Progress to Resolved
  • Assignee deleted (bertagaz)
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

intrigeri wrote:
> Also, note that this is the cheap, short term workaround, that will be obsoleted by the implementation I have in mind for Feature #12633.

Kept most of it, so it’s clear it’s working. Closing the ticket.