Commit 2f81091b authored by intrigeri's avatar intrigeri
Browse files

Release process: make it explicit which hash is used

One needs this info to compute hashes of the locally-built images.
parent 955a4f40
...@@ -709,7 +709,7 @@ to verify that Jenkins reproduced your images: ...@@ -709,7 +709,7 @@ to verify that Jenkins reproduced your images:
echo "https://jenkins.tails.boum.org/job/build_Tails_ISO_${RELEASE_BRANCH}/" echo "https://jenkins.tails.boum.org/job/build_Tails_ISO_${RELEASE_BRANCH}/"
2. Find the relevant build (probably the last one) 2. Find the relevant build (probably the last one)
and compare the hashes of the ISO and USB images built by Jenkins and compare the SHA512 hashes of the ISO and USB images built by Jenkins
(in the `tails-build-artifacts.shasum` build artifact) with the ones (in the `tails-build-artifacts.shasum` build artifact) with the ones
of the images you built. of the images you built.
......
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