9d5b82ebfb
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 Change-Id: I826947b1b358c4b04ba18135035292e135cce985
8 lines
359 B
Plaintext
8 lines
359 B
Plaintext
# NOTES(lourot):
|
|
# * We don't install charmcraft via pip anymore because it anyway spins up a
|
|
# container and scp the system's charmcraft snap inside it. So the charmcraft
|
|
# snap is necessary on the system anyway.
|
|
# * `tox -e build` successfully validated with charmcraft 1.2.1
|
|
|
|
cffi==1.14.6; python_version < '3.6' # cffi 1.15.0 drops support for py35.
|