Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #29741

Closed (moved)
(moved)
Open
Created Mar 12, 2019 by teor@teor

Work out how to fail chutney travis jobs when the tor repository is out of date or missing

In #27912 (moved), we configure a bunch of deb lines that depend on deb.torproject.org. But what happens when the repository is updated after a release?

We can either:

  • remember to update the travis config every release, or
  • work out how to make the jobs fail when they fall back to 0.2.9.14 (or Ubuntu security updates' current version)

Maybe there's a travis option that we could use?

This task does not need to be solved straight away.

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