Merge ~cjwatson/launchpad-buildd:lpcraft-common-output-directory into launchpad-buildd:master
Status: | Merged |
---|---|
Approved by: | Colin Watson |
Approved revision: | d380315758265bb244bae24f6e034ac953c92415 |
Merge reported by: | Otto Co-Pilot |
Merged at revision: | not available |
Proposed branch: | ~cjwatson/launchpad-buildd:lpcraft-common-output-directory |
Merge into: | launchpad-buildd:master |
Diff against target: |
265 lines (+57/-37) 5 files modified
debian/changelog (+6/-0) lpbuildd/ci.py (+13/-9) lpbuildd/target/run_ci.py (+6/-3) lpbuildd/target/tests/test_run_ci.py (+19/-19) lpbuildd/tests/test_ci.py (+13/-6) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jürgen Gmach | Approve | ||
Review via email: mp+427734@code.launchpad.net |
Commit message
Use a common output directory for all lpcraft jobs
Description of the change
In order to implement the `input` keyword in lpcraft, launchpad-buildd needs to use the same top-level output directory for each job so that lpcraft can find artifacts from previously-executed jobs. This is problematic with the current arrangements, because launchpad-buildd has to pass different `--output-
However, with https:/
This also gathers the `properties` file (currently unused) in a slightly different way, preparing for Launchpad to extract those output properties and store them in the database in a way that can conveniently be used downstream.
This mustn't be merged until https:/