Opened 20 months ago

Last modified 17 months ago

#29741 new defect

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

Reported by: teor Owned by:
Priority: Low Milestone:
Component: Core Tor/Chutney Version:
Severity: Minor Keywords: ex-sponsor19
Cc: teor Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor:


In #27912, we configure a bunch of deb lines that depend on 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 (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.

Child Tickets

Change History (2)

comment:1 Changed 20 months ago by teor

Parent ID: #27912

We don't need to do this before #27912 merges.

comment:2 Changed 17 months ago by gaba

Keywords: ex-sponsor19 added
Sponsor: Sponsor19-can

Remove sponsor 19 and add a keyword ex-sponsor19 to mark all the tickets that could have been in the scope of the sponsor.

Note: See TracTickets for help on using tickets.