Fix IUK generation in release process
(19:26:02) kibi: intrigeri: the loop is still buggy (19:26:13) kibi: also, it happily ignores failures and continues (19:26:21) kibi: chown: cannot access '"/home/kibi/work/clients/tails/release/isos/iuks/v2/Tails_amd64_4.0_to_4.2.1.iuk"': No such file or directory (19:29:54) kibi: I don't plan on fixing shell quoting issues (meaning testing the bugfixes) on my own (19:30:09) kibi: at least not right now; and I don't think I need you to do it instead, now. (19:30:35) kibi: maybe file a ticket? I might take a little break while the IUKs are grinding.
Release process: simplify local IUKs generation (refs: #17415)
This code block was getting awfully complicated and did not work in my shell
configuration, so let's instead delegate the most complex logic and error
handling to the existing wrap_tails_create_iuks Python script (used by the
build_IUKs Jenkins job) and keep only very simple shell code in here.
Incidentally, this has an extra advantage: wrap_tails_create_iuks will download
any ISO that it can't find locally, which can be useful. Our doc asks the RM to
download such images at the beginning of their shift, but it's better not to
rely on this:
- We sometimes split the release process in 2+ pieces; whoever handles
this part might not be the one who did the earlier steps.
- Between the beginning of a release cycle and release time, the RM might have
deleted old images to save disk space locally.
kibi's fixes break the "Build the Incremental Upgrade Kits locally" code block in my shell environment. Workaround'ed by running it under
/bin/sh. This code block is getting awfully complicated and as we can see, shell-config-dependent, so IMO it's a good candidate to migrate from inline shell snippet to a Python script.
- Status changed from In Progress to Needs Validation
- Assignee changed from intrigeri to anonym
OK, I have something.
anonym, please either review this ahead of the 4.3 release process, or just test it while you'll go through this step (the plan is still that I'll be around to help if anything goes wrong).
Note that https://tails.boum.org/contribute/working_together/roles/release_manager/ has new stuff ("The ISO images for […]") so you cannot skip the whole section under the "business as usual" assumption.