Merge lp://staging/~abentley/ci-director/independent-output into lp://staging/ci-director
Proposed by
Aaron Bentley
| Status: | Merged |
|---|---|
| Merged at revision: | 163 |
| Proposed branch: | lp://staging/~abentley/ci-director/independent-output |
| Merge into: | lp://staging/ci-director |
| Prerequisite: | lp://staging/~abentley/ci-director/refactor |
| Diff against target: |
245 lines (+202/-2) 3 files modified
cidirector/tests/test_cidirector.py (+31/-2) cidirector/tests/test_update_outcome.py (+68/-0) cidirector/update_outcome.py (+103/-0) |
| To merge this branch: | bzr merge lp://staging/~abentley/ci-director/independent-output |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Curtis Hovey (community) | code | Approve | |
|
Review via email:
|
|||
Commit message
Begin implementing update-outcome script.
Description of the change
This branch begins implementing the update-outcome script.
The idea of this script is that it can be used to update the outcomes of revision builds, separately from the main ci-director script.
It scans Jenkins. For each [ci-director] job, it retrieves data on new builds.
New builds are those builds that were not considered "complete" in the update-outcome run. This includes builds which have completed since the last update-outcome run, and those which are still building.
The retrieved data is organized by revision-build, job-name and build number.
Still to come: generating data in a format suitable for juju-reports and uploading it to S3.
To post a comment you must log in.
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
thank you. This was a bit hard to digest. Can you add some doc comments that explain what callables are doing?