
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 - Unit test fix Depends-On: https://review.opendev.org/c/openstack/charm-keystone/+/830986 Depends-On: https://review.opendev.org/c/openstack/charm-interface-keystone/+/830988 Change-Id: Iadd11634d1fe44731ecf0a6104561b4aeebff23f Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
48 lines
1.1 KiB
YAML
48 lines
1.1 KiB
YAML
type: charm
|
|
|
|
parts:
|
|
charm:
|
|
build-packages:
|
|
- tox
|
|
- git
|
|
- python3-dev
|
|
- libffi-dev
|
|
- libssl-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:
|
|
- name: ubuntu
|
|
channel: "20.04"
|
|
architectures: [amd64]
|
|
- name: ubuntu
|
|
channel: "20.04"
|
|
architectures: [arm64]
|
|
- name: ubuntu
|
|
channel: "20.04"
|
|
architectures: [ppc64el]
|
|
- name: ubuntu
|
|
channel: "20.04"
|
|
architectures: [s390x]
|
|
- name: ubuntu
|
|
channel: "22.04"
|
|
architectures: [amd64]
|
|
- name: ubuntu
|
|
channel: "22.04"
|
|
architectures: [arm64]
|
|
- name: ubuntu
|
|
channel: "22.04"
|
|
architectures: [ppc64el]
|
|
- name: ubuntu
|
|
channel: "22.04"
|
|
architectures: [s390x]
|