lp:~gnuoy/ubuntu-openstack-ci/use-venv-tox

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:ubuntu-openstack-ci at revision 443

Frode Nordahl: Approve on 2020-11-05

Diff: 11 lines (+4/-0)

1 file modified

deploy/templates/oscirc (+4/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

443. By Liam Young on 2020-11-05

Tox 2.3.1 (xenial distro version) pulls pip tip which is currently 20.3.b1.
The combination of the two makes pip spin consuming all available memory. So,
use tox from a venv (/var/lib/jenkins/.local/bin) instead.

442. By Liam Young on 2020-10-14

[aurelien-lourot, r=gnuoy] Set Ironic image location

441. By Liam Young on 2020-09-28

[chris.macnaughton, r=gnuoy] Add swift IP for Serverstack resources

440. By Chris MacNaughton on 2020-09-14

[fnordahl, r=chris.macnaughton] Use ctime rather than mtime for cleanup

439. By Chris MacNaughton on 2020-08-31

[aurelien-lourot, r=chris.macnaughton] Support func-test-pr branch names with several slashes

438. By Liam Young on 2020-08-20

[chris.macnaughton, r=gnuoy] Allow a tox target to be passed into a run

437. By Liam Young on 2020-08-18

[gnuoy, r=admcleod] Ensure operator charms are built and deploy tests run

436. By Liam Young on 2020-08-18

[gnouy,r=chris.macnaughton] Add operator charm support to unit test runner

435. By Liam Young on 2020-08-17

[gnuoy, r=aurelien-lourot] Support Operator framework charms

The build process for an Operator framework charm that uses the
charmcraft for building is a zip file containing the charm. During the build
phase a new variable BUILT_ASSET_FILE is used to track the location of this
file.

The mechanism for storing the built charm for consumption by later tests
is mostly the same as for other built charms accept the tar ball created to
store the built charm contains only the zip file. There is obviously not
much point in tar'ing up a zip file but in this case it does not do any
harm and minimises the number changes needed to support the new charms.

Once the previously stored charm is retrieved by a future step it is
untar'd and then the zip file is unzipped into a new 'unpacked' directory.
The zip file is then copied into that directory and the charm is then
ready for its functional tests to be run.

434. By Liam Young on 2020-07-15

[gnuoy, r=ajkavanagh] Add support for charmed-openstack-tests