Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P puppet-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 and registries
    • Packages and 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
  • emmapeel
  • puppet-tails
  • Repository
Switch branch/tag
  • puppet-tails
  • manifests
  • check_mirrors
  • cronjob.pp
Find file BlameHistoryPermalink
  • intrigeri's avatar
    Ensure only one instance of check-mirrors.rb runs concurrently · 9dbdc6f5
    intrigeri authored Jun 27, 2020
    Now that we're running check-mirrors.rb 4 times more often,
    there's greater chances that 2 of them end up running at the same time.
    Let's avoid having to reason about how check-mirrors.rb manages
    shared resources such as its failures.json state file.
    
    refs: tails/tails#17755
    9dbdc6f5