Merge ~cjwatson/launchpad:fix-build-tarball-assets into launchpad:master
Status: | Merged |
---|---|
Approved by: | Colin Watson |
Approved revision: | 97990c559e9c4a7234c78b2aa238523c432a2abf |
Merge reported by: | Otto Co-Pilot |
Merged at revision: | not available |
Proposed branch: | ~cjwatson/launchpad:fix-build-tarball-assets |
Merge into: | launchpad:master |
Diff against target: |
26 lines (+2/-2) 2 files modified
Makefile (+1/-1) utilities/build-tarball (+1/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jürgen Gmach | Approve | ||
Review via email: mp+441863@code.launchpad.net |
Commit message
Move asset build to be local to build-tarball
Description of the change
The `build_wheels_only` target in the `Makefile` is used by both legacy deployments (via a complex chain of systems that include a call to `make build_wheels`) and Juju deployments (via a Jenkins job that calls `make publish-tarball`). We need `make publish-tarball` to build assets in order to support a future charm, but `make build_wheels` can't do so because the legacy build machine doesn't have the right dependencies installed - and we probably don't want to re-engineer those deployments too heavily anyway.
Moving this to the `build-tarball` script and reverting the `Makefile` changes lets us make things work the way they need to for Juju deployments, while fixing legacy deployments.