Commit d163abc0 authored by intrigeri's avatar intrigeri
Browse files

Release process: upload images to git-annex earlier (refs: #15287)

The Jenkins build_IUKs job needs them.
parent 404679dc
......@@ -854,7 +854,26 @@ Build the Incremental Upgrade Kits locally
done
This command can take a long time. In parallel, while it is running,
you can build the Incremental Upgrade Kits on Jenkins:
you can follow the next 2 steps:
- Push the images to our ISO history git-annex repo
- Build the Incremental Upgrade Kits on Jenkins
ISO history
-----------
Push the released ISO and USB images and their artifacts (`.buildlog`,
`.build-manifest`, and `.packages` files) to our Tails ISO history git-annex
repo, so that:
- The Jenkins `build_IUKs` can fetch them.
- Our isotesters can fetch them from there for their testing
How to do so is described in the `ISO_history.mdwn` document in the RM team's
Git repo.
Then, wait (a few minutes) until the images appear
on <https://iso-history.tails.boum.org/>.
<a id="build-iuks-on-jenkins"></a>
......@@ -1214,13 +1233,6 @@ Now you can announce and seed the Torrents for the release you're preparing:
Test that you can start downloading the ISO and USB images with a BitTorrent client.
ISO history
-----------
Push the released ISO and USB images and their artifacts (`.buildlog`, `.build-manifest`, and `.packages` files) to our Tails ISO history git-annex repo, so that
our isotesters can fetch them from there for their testing. How to do so
is described in the `ISO_history.mdwn` document in the RM team's Git repo.
Testing
=======
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment