Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S sysadmin
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 84
    • Issues 84
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • tails
  • sysadmin
  • Issues
  • #17775
Closed (moved) (moved)
Open
Issue created Oct 30, 2020 by intrigeri@intrigeriMaintainer0 of 3 checklist items completed0/3 checklist items

GitLab CI: build website

  • Iteration 1: merely migrate what we have on Jenkins (job definition, that simply runs ./build-website) to GitLab CI: build the website on the master branch.

  • Iteration 2: also run this job on MRs whose target branch is master, in order to identify website build breakage before deployment.

  • 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
Edited Sep 22, 2022 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking