9c58c4bb2c
Due to a build problem with the reactive plugin, this change falls back
on overriding the steps and doing a manual build, but it also ensures
the CI system builds the charm using charmcraft. Changes:
- add a build-requirements.txt
- modify charmcraft.yaml
- modify osci.yaml
-> indicate build with charmcraft
- modify tox.ini
-> tox -e build does charmcraft build/rename
-> tox -e build-reactive does the reactive build
- modify bundles to use the <charm>.charm artifact in tests.
and fix deprecation warning re: prefix
- tox inception to enable tox -e func-test in the CI
- Pin everything in wheelhouse.txt for bionic and focal support.
This will need updating when the charm channels are created.
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/778
Change-Id: I1fc6374f6201a6ee5dbe46bd23a71a2f7372bbcf
34 lines
876 B
YAML
34 lines
876 B
YAML
type: charm
|
|
|
|
parts:
|
|
charm:
|
|
build-packages:
|
|
- tox
|
|
- git
|
|
- python3-dev
|
|
override-build: |
|
|
apt-get install ca-certificates -y
|
|
tox -e build-reactive
|
|
override-stage: |
|
|
echo "Copying charm to staging area: $CHARMCRAFT_STAGE"
|
|
NAME=$(ls $CHARMCRAFT_PART_BUILD/build/builds)
|
|
cp -r $CHARMCRAFT_PART_BUILD/build/builds/$NAME/* $CHARMCRAFT_STAGE/
|
|
override-prime: |
|
|
# For some reason, the normal priming chokes on the fact that there's a
|
|
# hooks directory.
|
|
cp -r $CHARMCRAFT_STAGE/* .
|
|
|
|
bases:
|
|
- build-on:
|
|
- name: ubuntu
|
|
channel: "20.04"
|
|
architectures:
|
|
- amd64
|
|
run-on:
|
|
- name: ubuntu
|
|
channel: "20.04"
|
|
architectures: [amd64, s390x, ppc64el, arm64]
|
|
- name: ubuntu
|
|
channel: "22.04"
|
|
architectures: [amd64, s390x, ppc64el, arm64]
|