Bug #16026

Jenkins reproducibly_build jobs lack ISOs and their checksums

Added by anonym 2018-10-03 16:35:14 . Updated 2019-03-08 14:18:19 .

Status:
Rejected
Priority:
Normal
Assignee:
anonym
Category:
Continuous Integration
Target version:
Start date:
2018-10-03
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

See e.g. Jenkins’ otherwise successful attempt for Tails 3.9.1: https://jenkins.tails.boum.org/job/reproducibly_build_Tails_ISO_stable/456/

12:53:04 + sudo TMPDIR=/var/lib/jenkins/workspace/reproducibly_build_Tails_ISO_stable diffoscope --text /var/lib/jenkins/workspace/reproducibly_build_Tails_ISO_stable/build-artifacts/diffoscope.txt --html /var/lib/jenkins/workspace/reproducibly_build_Tails_ISO_stable/build-artifacts/diffoscope.html --max-report-size 262144000 --max-diff-block-lines 10000 --max-diff-input-lines 10000000 /var/lib/jenkins/workspace/reproducibly_build_Tails_ISO_stable/build-artifacts/1/tails-amd64-3.9.1.iso /var/lib/jenkins/workspace/reproducibly_build_Tails_ISO_stable/build-artifacts/2/tails-amd64-3.9.1.iso

Here we see that the images are 1/*.iso and 2/*.iso.

12:53:09 + ls -d tails-* 1/tails-build-env.list 2/tails-amd64-3.9.1.iso.apt-sources 2/tails-amd64-3.9.1.iso.build-manifest 2/tails-amd64-3.9.1.iso.buildlog 2/tails-amd64-3.9.1.iso.packages diffoscope.*
12:53:09 ls: cannot access 'tails-*': No such file or directory
12:53:09 ls: cannot access 'diffoscope.*': No such file or directory
12:53:09 + sha512sum 1/tails-build-env.list
12:53:09 + sha512sum 2/tails-amd64-3.9.1.iso.apt-sources
12:53:09 + sha512sum 2/tails-amd64-3.9.1.iso.buildlog
12:53:09 + sha512sum 2/tails-amd64-3.9.1.iso.build-manifest
12:53:09 + sha512sum 2/tails-amd64-3.9.1.iso.packages
12:53:09 + gpg --batch --detach-sign --armor tails-build-artifacts.shasum


Here it the ls -d tails-* part looks wrong, it should be something like {1,2}/tails-*.iso.

Subtasks

History

#1 Updated by intrigeri 2018-10-10 21:02:03

  • Assignee deleted (intrigeri)

#2 Updated by intrigeri 2018-10-10 21:08:39

  • Assignee set to anonym
  • QA Check set to Info Needed

> Here it the ls -d tails-* part looks wrong, it should be something like {1,2}/tails-*.iso.

Indeed. Technically, that might be a bug with the CI jobs that were set up as part of our reproducible builds project, and thus could be listed on https://labs.riseup.net/code/projects/tails/issues?query_id=269. But I’m not sure and won’t make this decision myself.

Please:

  1. Describe the actual impact of the problem. E.g. whether it breaks something we have documented as working, whether it is confusing and made you waste your time, or what not.
  2. Reassign to our team manager (u) so she decides what to do with this. AFAIK we’ve had no issue with this for a year so maybe it’s no big deal, should not be part of SponsorT, and should instead be added to the list of known UX pain points with our CI, which can be useful whenever we’ll be able to work on this sort of things again.

#3 Updated by Anonymous 2019-03-08 14:18:19

  • Status changed from Confirmed to Rejected

We still don’t know what the actual impact of the problem is → rejecting. Please reopen when you can explain it.