Skip to content

GitLab

  • Menu
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 87
    • Issues 87
    • 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
Open
Created Oct 30, 2020 by intrigeri@intrigeriMaintainer

GitLab CI: build website

A first iteration could be to merely migrate what we have on Jenkins (job definition, that simply runs ./build-website) to GitLab CI: build the website on the master branch.

A second iteration could be to also run this job on MRs whose target branch is master, in order to identify website build breakage before deployment.

A third iteration could be to run this job on all branches/MRs. In order to avoid wasting resources, we should have a mechanism to avoid building needlessly. For example, while building Tails images, we do this: https://gitlab.tails.boum.org/tails/tails/-/blob/stable/auto/scripts/website-cache.

cc @zen

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking