Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • P puppet-tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • emmapeel
  • puppet-tails
  • Repository
  • puppet-tails
  • manifests
  • tester
  • check_po.pp
Find file Blame History Permalink
  • Zen Fu's avatar
    Use jenkins-tools.git from its new location (gitlab-migration#97) · c69ec24e
    Zen Fu authored Jul 24, 2020
    Maintaining HTTPS for now, as it's not a regression in this case.
    
    We can probably use the role-jenkins-isotester user for this once the
    SSH key of GitLab has been deployed in isotesters. I'm not sure if yet
    another key would have to be added that user's config in GitLab.
    
    See: https://salsa.debian.org/tails-team/gitlab-migration/-/issues/97
    c69ec24e