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: I9b41911cdc3f8e6c327d68df50007b5223aaed34
Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
Symbolic link
1 line
17 B
YAML
Symbolic link
1 line
17 B
YAML
src/metadata.yaml |