Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Zen Fu
  • tails
  • Repository
Switch branch/tag
  • tails
  • config
  • gitlab-triage
  • Dockerfile
Find file BlameHistoryPermalink
  • intrigeri's avatar
    Automate post-release GitLab updates, using gitlab-triage (#17589) · 9e11debf
    intrigeri authored Jun 06, 2020
    We will use gitlab-triage to solve other problems soon
    (https://salsa.debian.org/tails-team/gitlab-migration/-/issues/54),
    and it's the perfect tool for the job, so it makes sense
    to start using it here as well.
    
    Since gitlab-triage is not in Debian, in order to be compliant with the security
    policies applicable to Release Managers:
    
     - run gitlab-triage in Docker
     - ensure we always use the latest version of gitlab-triage,
       in a fresh Docker image based on the latest version of debian:stable
    9e11debf