Merge lp://staging/~sinzui/juju-ci-tools/build-from-s3 into lp://staging/juju-ci-tools
| Status: | Merged |
|---|---|
| Merged at revision: | 1908 |
| Proposed branch: | lp://staging/~sinzui/juju-ci-tools/build-from-s3 |
| Merge into: | lp://staging/juju-ci-tools |
| Diff against target: |
260 lines (+113/-56) 2 files modified
build_juju.py (+30/-16) tests/test_build_juju.py (+83/-40) |
| To merge this branch: | bzr merge lp://staging/~sinzui/juju-ci-tools/build-from-s3 |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Juju Release Engineering | Pending | ||
|
Review via email:
|
|||
Description of the change
Build juju agents from s3 artifacts.
Many of the canonical machines do not have access to the jenkins jobs to pickup assets to build. They do have access to s3. This branch switched build_juju.py to use s3ci.py instead of jujuci.py. These changes have been used in anger to build juju agents for s390x, ppc64el, arm64, and amd64.
build-
build-
build-
build-
build_juju.py now needs to know the s3 config to get the build-revision's juju tarfile. It also needs to know the architecture to pass to the crossbuild.py script. Only the "ubuntu-agent" subcommand takes the arch option, so we only append --goarch when needed.
This cannot merge without me also updating these jobs to pass in the s3 config.
build-centos
build-
build-win-agent
build-
