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
13 lines
595 B
Plaintext
13 lines
595 B
Plaintext
# This file is managed centrally by release-tools and should not be modified
|
|
# within individual charm repos. See the 'global' dir contents for available
|
|
# choices of *requirements.txt files for OpenStack Charms:
|
|
# https://github.com/openstack-charmers/release-tools
|
|
#
|
|
|
|
# Need tox to be available from tox... inception yes, but its a workaround for now
|
|
tox
|
|
|
|
# Functional Test Requirements (let Zaza's dependencies solve all dependencies here!)
|
|
git+https://github.com/openstack-charmers/zaza.git#egg=zaza
|
|
git+https://github.com/openstack-charmers/zaza-openstack-tests.git#egg=zaza.openstack
|