Merge lp://staging/~fginther/ubuntu-ci-services-itself/lander-pass-artifacts into lp://staging/ubuntu-ci-services-itself
| Status: | Merged |
|---|---|
| Approved by: | Andy Doan |
| Approved revision: | 329 |
| Merged at revision: | 350 |
| Proposed branch: | lp://staging/~fginther/ubuntu-ci-services-itself/lander-pass-artifacts |
| Merge into: | lp://staging/ubuntu-ci-services-itself |
| Diff against target: |
324 lines (+203/-15) 5 files modified
image-builder/imagebuilder/run_worker.py (+8/-2) lander/bin/lander_service_wrapper.py (+9/-6) lander/bin/ticket_api.py (+43/-4) lander/lander/tests/test_ticket_api.py (+132/-0) test_runner/tstrun/run_worker.py (+11/-3) |
| To merge this branch: | bzr merge lp://staging/~fginther/ubuntu-ci-services-itself/lander-pass-artifacts |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Andy Doan (community) | Approve | ||
| PS Jenkins bot (community) | continuous-integration | Approve | |
|
Review via email:
|
|||
Commit message
Enable the lander to recognize artifacts inside the progress update message and register them on the ticket.
Description of the change
Enable the lander to recognize artifacts inside the progress update message and register them on the ticket.
I've also updated the image builder and test runner to create artifacts with the new naming scheme (so that the web-ui can group artifacts by workflow step).
The progress update message must have the following:
artifacts: [{
'name': artifact_name,
'reference': artifact_url,
'type': one of 'LOGS', 'RESULT', 'IMAGE'
},
...
]
The lander will only register artifact_name once, if it appears again, it will be ignored. This is to allow the components to continuously send back the artifact list in the progress updates and not result in duplicate entries in the ticket.
| Francis Ginther (fginther) wrote | # |
| PS Jenkins bot (ps-jenkins) wrote | # |
Here's an artifact with the logs from the image builder and test runner attached:
http://