Merge lp://qastaging/~doanac/uci-engine/lander-flows into lp://qastaging/uci-engine
Status: | Merged |
---|---|
Approved by: | Francis Ginther |
Approved revision: | 463 |
Merged at revision: | 478 |
Proposed branch: | lp://qastaging/~doanac/uci-engine/lander-flows |
Merge into: | lp://qastaging/uci-engine |
Diff against target: |
667 lines (+182/-156) 4 files modified
lander/bin/lander_process_ticket.py (+16/-28) lander/bin/lander_service_wrapper.py (+34/-47) lander/lander/tests/test_service_wrapper.py (+47/-81) lander/lander/workflow.py (+85/-0) |
To merge this branch: | bzr merge lp://qastaging/~doanac/uci-engine/lander-flows |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Francis Ginther | Approve | ||
PS Jenkins bot (community) | continuous-integration | Approve | |
Review via email: mp+218150@code.qastaging.launchpad.net |
Commit message
lander: introduce beginnings of a "workflow"
This moves us more towards being able to give the lander a
specific workflow for it to iterate through. For now its
hard-coded, but we could expand on this get the required workflow
of a ticket from the ticket-system.
This creates a results file / workflow that looks like:
{
'ppa_
'progress_
'ticket_id': ticket_id,
'ts_url': ts_url,
'steps': [
{'name': 'ppa_assigner'},
{'name': 'bsbuilder'},
],
}
Description of the change
Here's a view of the file upon completion of a ticket:
https:/
PASSED: Continuous integration, rev:462 s-jenkins. ubuntu- ci:8080/ job/uci- engine- ci/579/
http://
Executed test runs:
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/uci- engine- ci/579/ rebuild
http://