Allow independent triggering of ci and autolanding jobs for entire stacks
Bug #1237015 reported by
Francis Ginther
on 2013-10-08
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | cupstream2distro Configuration |
High
|
Francis Ginther | ||
Bug Description
cu2d-trigger supports 3 trigger modes:
1) trigger ci for a single branch
2) trigger autolanding for a single branch
3) trigger both for a stack
There is a need to support independent triggering of ci and autolanding jobs per stack. For example, this would allow us to shutoff autolanding while still allowing MPs to be tested via ci.
Related branches
lp:~fginther/cupstream2distro-config/independent-triggering
- Joe Talbott (community): Approve on 2013-10-09
- Francis Ginther: Resubmit on 2013-10-08
- PS Jenkins bot: Approve (continuous-integration) on 2013-10-08
-
Diff: 350 lines (+128/-52)2 files modifiedc2dconfigutils/cu2dTrigger.py (+37/-27)
tests/test_cu2dTrigger.py (+91/-25)
Francis Ginther (fginther)
on 2013-10-08
| Changed in cupstream2distro-config: | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Francis Ginther (fginther) |
| PS Jenkins bot (ps-jenkins) wrote : | #1 |
| Changed in cupstream2distro-config: | |
| status: | In Progress → Fix Committed |
To post a comment you must log in.
Fix committed into lp:cupstream2distro-config at revision None, scheduled for release in cupstream2distr