Commit 9381d011 authored by anonym's avatar anonym
Browse files

Merge branch 'feature/17746-improvements-from-4.7-release-process' into 'stable'

Release process improvements from 4.7 release

See merge request !38
parents aadc69d4 01606bb4
......@@ -677,6 +677,10 @@ suite should be ready, so it is time to:
Our build system will apply the correct compression settings automatically
so don't bother setting it yourself.
1. Make sure the Jenkins build starts. Until the hook is back in place
([[!tails_ticket 17745]]), starting it manually may avoid up to 15
minutes of waiting.
1. Compare the new build manifest with the one from the previous,
almost-final build:
......@@ -923,6 +927,21 @@ that is not present locally yet):
Build the Incremental Upgrade Kits locally
------------------------------------------
You're encouraged to enable parallelism to avoid waiting for a very
long, serial build (which is still the default at the moment). As
discussed in [[!tails_ticket 17657]], it seems running as many jobs as
there are physical cores is a nice rule of thumb.
For example, set:
JOBS="--jobs 4"
or, attempt to automatically set it to the number of physical cores:
JOBS="--jobs $(grep '^core id' /proc/cpuinfo | sort -u | wc -l)"
before starting the wrapper from `puppet-tails`:
(
set -eu
WORK_DIR=$(mktemp -d)
......@@ -930,6 +949,8 @@ Build the Incremental Upgrade Kits locally
PUPPET_TAILS_REMOTE=$(echo -n "${TAILS_REMOTE?:}" | perl -p -E 's,:tails(:?[.]git)?\z,:puppet-tails,')
cd "${WORK_DIR?:}"
git clone "$PUPPET_TAILS_REMOTE"
sudo -l
time \
./puppet-tails/files/jenkins/slaves/isobuilders/wrap_tails_create_iuks \
--tails-git-remote "file://${RELEASE_CHECKOUT?:}/.git" \
--tails-git-commit "${TAG?:}" \
......@@ -939,10 +960,10 @@ Build the Incremental Upgrade Kits locally
--output-dir "${IUKS_DIR?:}" \
--source-versions "${IUK_SOURCE_VERSIONS?:}" \
--new-version "${VERSION?:}" \
--verbose
--verbose ${JOBS:-}
cd "${IUKS_DIR?:}"
sha256sum Tails_amd64_*_to_${VERSION?:}.iuk > "${IUKS_HASHES?:}"
)
)
This command takes a long time. In parallel, while it is running,
you can follow the next step:
......@@ -1658,6 +1679,8 @@ website:
git push origin master:master \
)
Remember to also push to lizard until hooks are in place in GitLab.
The release is now public! Woo!
Bug tracker
......@@ -1813,7 +1836,7 @@ If you just released a final release
git submodule update --init && \
bare_repo=$(mktemp -d) && \
git clone --bare --reference "${MASTER_CHECKOUT:?}" \
git@gitlab.tails.boum.org:tails/tails \
git@gitlab-ssh.tails.boum.org:tails/tails \
"${bare_repo:?}" && \
PYTHONPATH=lib/python3 ./bin/delete-merged-git-branches \
--repo "${bare_repo:?}" && \
......@@ -1935,7 +1958,7 @@ If you just released an RC
1. Follow the "Verify that the snapshots used in the release branch
are ok" step for final releases, above.
1. Make sure Jenkins manages to build all updated major branches:
<https://jenkins.tails.boum.org/>.
<https://jenkins.tails.boum.org/view/RM/>.
1. In [[contribute/calendar]], remove the entries about the version that you've
just released.
......
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