lp:~fnordahl/ubuntu-openstack-ci/bug-1733984

Branch merges

Propose for merging

No branches dependent on this one.

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

Frode Nordahl: Approve on 2020-09-14

Aurelien Lourot (community): Approve on 2020-09-14

Diff: 12 lines (+2/-2)

1 file modified

run/job-parts/osci_job_common.sh (+2/-2)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1733984: charm fails to build

Medium

Fix Released

Link a bug report

Related blueprints

440. By Frode Nordahl on 2020-09-14

Use ctime rather than mtime for cleanup

  During various build processing on task executors archives will be
  extracted to /tmp (pip, charm tools etc.). The mtime for the files
  extracted come from the archive itself and stems from the upstream
  build process. We most certainly would be more interested in when
  the files were changed on the local file system (ctime) for
  knowing what to clean up.

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

433. By Liam Young on 2020-06-24

[aurelien-lourot, r=gnuoy] Delegate Arista image download to Zaza

432. By Liam Young on 2020-06-23

[aurelien-lourot, r=gnuoy] Add arista image support

431. By Liam Young on 2020-06-16

[gnuoy, r=chris.macnaughton] A recent change to z-o-t switched proxy env variable

A recent change to zaza-openstack-tests switched the tests from using
OS_TEST_HTTP_PROXY to TEST_HTTP_PROXY *1. This has caused some failures *2
as osci is still using the old variablr.

*1 https://github.com/openstack-charmers/zaza-openstack-tests/commit/1a784f5b049fc996b2f0cf584d983d002df1a000
*2 https://review.opendev.org/#/c/735106/