Remove pins.
Properly format passenv list.
Drop the outer tox.ini func-target hack.
Drop the incepted tox in src/test-requirements.txt.
Drop pip.sh script.
Change-Id: I25dec5d1853a5aeb686df353d7c661f4a6eb5b69
Charmcraft 2.1 provides the required functionality to build the
charm using the reactive plugin.
Add missing `kinetic` series in src/metadata.yaml.
Drop the `build-rective` target, old charm-tools environment
variables and redundant minversion in tox.ini.
Fixup the bases configuration and make associated changes to test
bundles.
Change-Id: I559e49ab80ca6de8b42192e1b961448a4522ce86
* sync charm-helpers to classic charms
* change openstack-origin/source default to zed
* align testing with zed
* add new zed bundles
* add zed bundles to tests.yaml
* add zed tests to osci.yaml and .zuul.yaml
* update build-on and run-on bases
* add bindep.txt for py310
* sync tox.ini and requirements.txt for ruamel
* use charmcraft_channel 2.0/stable
* drop reactive plugin overrides
* move interface/layer env vars to charmcraft.yaml
Change-Id: I2cb698f719106e54b06009f24ea47259419e9cad
Charms for OpenStack Yoga supports both Ubuntu Focal and Jammy
which means Python 3.8 and Python 3.10. Managing dependencies
across those two versions is non-trivial and we need to build
the charm on the series the charm is supposed to support.
Switch to using a binary build which allows pip's dependency
resolution to work.
Change-Id: Ibfe317d1056e44baa32c414d33f54d656887d2a1
- charmcraft: build-on 20.04 -> run-on 20.04/22.04 [*archs]
- Refresh tox targets
- Drop impish bundles and OSCI testing
- Add jammy metadata
Drop NRPE from Jammy bundles as the charm is not updated to
support Python 3.10 yet.
Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/742
Change-Id: Idd8a2e2387da0012ba78d50960630e7a1472dc8e
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: I3199f7dba089767d27638ec3ca2b126a083fbe82
* charm-helpers sync for classic charms
* sync from release-tools
* switch to release-specific zosci functional tests
* run focal-ussuri as smoke tests
* remove trusty, xenial, and groovy metadata/tests
* drop py35 and add py39
Change-Id: I33a8831474633c5516a956fec86d13e333a03b76
* charm-helpers sync for classic charms
* build.lock file for reactive charms
* ensure tox.ini is from release-tools
* ensure requirements.txt files are from release-tools
* On reactive charms:
- ensure stable/21.04 branch for charms.openstack
- ensure stable/21.04 branch for charm-helpers
Change-Id: Ia060b7ebef8585b0976afaf7b8c26f18abdd7b15
* Update requirements.txt to pin charm-tools to 2.8.3
* Update tox.ini to change the build parameters.
* This upgrades from <2.7 which adds reproducible charms
* Bug was fixed that controlled the default output directory
doesn't get 'builds' appended. The tox change puts it
back so that stable & master both build to the same
directory. This may be reviewed in the future.
Change-Id: I716de45b98f97d19138d424fc0279a5a058b30c1
* charm-helpers sync for classic charms
* charms.ceph sync for ceph charms
* rebuild for reactive charms
* sync tox.ini files as needed
* sync requirements.txt files to sync to standard
Change-Id: I077b698c3302dc32a5ffdca0e86dade9f49d7b96
The two charms 'ovn-chassis' and 'ovn-dedicated-chassis' are apart
from metadata identical. Consume the shared code from layer.
Change-Id: Ib133c805151cf66c5316df38c33ea6d20a38fa2b
