Bug #16584

release_process: maybe move setting MATCHING_JENKINS_BUILD_ID higher?

Added by CyrilBrulebois 2019-03-21 00:03:08 . Updated 2019-03-21 09:43:03 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2019-03-21
Due date:
% Done:

100%

Feature Branch:
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

The first time one is supposed to check Jenkins happens here:

1. <a id="reproducibility-sanity-check-iso"></a>
   Let's sanity check that Jenkins reproduced your images.

   Visit the URL printed by this command:

       echo "https://jenkins.tails.boum.org/job/build_Tails_ISO_${RELEASE_BRANCH}/"

   Find the job (probably the last one)
   and make sure the ISO and USB images built by Jenkins:

   - were built from the correct Git commit
   - have the same file size as the images you built
   - have the same hash (in the `.shasum` file) as the images you built

but one is only asked to set/remember the proper job ID later on, in:

Publish the ISO, IMG, and IUKs over HTTP
----------------------------------------
[…]
Pick a build from `$RELEASE_BRANCH` that produced identical ISO and USB images
to the ones you've built locally (`XXX` must be the job ID, i.e.
an integer):

    MATCHING_JENKINS_BUILD_ID=XXX

Maybe we could suggest setting the right variable the first time around?


Subtasks


History

#1 Updated by CyrilBrulebois 2019-03-21 00:23:47

  • Subject changed from release_process: maybe move setting JENKINS… higher? to release_process: maybe move setting MATCHING_JENKINS_BUILD_ID higher?

(Adjusting title, I failed to update it when filing the ticket, once I found the exact variable name.)

#2 Updated by intrigeri 2019-03-21 09:43:03

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

Applied in changeset commit:tails|e75bc8a94bab84862f9c4b87e417a664ad497f1e.