GitLab CI: build website for QA
-
Iteration 1: merely migrate what we have on Jenkins (job definition) to GitLab CI: build the website on the master
branch (!924 (merged)) -
Iteration 2: also run this job on MRs whose target branch is master
, in order to identify website build breakage before deployment (!924 (merged)) -
Cleanup: -
Remove the build_website_master
Jenkins job: jenkins-jobs!5 (merged) -
Stop including tails::website::builder
on isobuilders (modules/local/manifests/node/isobuilder.pp
): asked the reviewer to do so after merging jenkins-jobs!5 (merged)
-
-
Iteration 3: run this job on all relevant branches/MRs, without wasting resources. For example: - Only build if files in
wiki/src
are modified - Caching: while building Tails images, we use this: https://gitlab.tails.boum.org/tails/tails/-/blob/stable/auto/scripts/website-cache
- Only build if files in
Edited by intrigeri