The correct path for the coverage logs is cover/ not coverage/, fix this
in the {name}-coverage job when uploading these coverage details to
swift.
Change-Id: I6484572e8adcc9495969ae77653c0f540a348680
Duplicate the test-results publisher for swift. This will capture
all logs from the job which is a superset of what was being
uploaded.
Change-Id: If1e7baf5dad8601c7489366688ccb02d7fc1c742
Enable swift logs for the simple python jobs. Still to come is a
macro for swift uploading test-results
Change-Id: Ie907f464ddf114583db4d08d09379c1af6d104c1
These are no longer being used to run jobs, so clean up references
to them.
Change-Id: Iac7ffde66a2d5d1a1361ed9bcadb9144e034f10f
Depends-On: I40d5d09f28ef53583d239d2e852e9c50b5962cf8
Need an extra two spaces to properly format the yaml and pass the
upload_source parameter through to the
zuul_swift_upload_logs_with_console macro.
Change-Id: I52abaed67b6730d7c5080ebc3c393cb2567bef29
Use postbuildscript publishers to capture jobs that have failed
by ensuring that logs are uploaded even if the build has exited.
Keep the build macros as the postbuildscript needs builders to
execute and they also aren't strictly just for use as a publisher.
Change-Id: I21463f89281911dff6efda31e754bdc7b3266e24
We had the logic in the post build script conditions inverted. We
unfortunately need to say onsuccess: False and onfailure: False to make
this run on every job regardless of its build status.
This is because the plugin treats those options as IFFs with onsuccess
being evaluated first. So if onsuccess is set to True then the post
build script will run if and only if the build status was successful.
Similar story for onfailure. If we set them both to false then neither
success nor failure is checked and we should run the script on all
builds.
Change-Id: I70fd948e239e8a5007b0f5813c9d5757a1742abe
Stop using run-unittests.sh. It creates confusion when people create
jobs. Instead standardize on run-tox.sh. This means rewriting all the
jobs that use run-unittests.sh to use run-tox.sh.
Note that this depends on the parent change to merge first and have all
our slave images rebuilt prior to merging this change.
Change-Id: Ib81403c25485b120f48080a59f1894dc2130c05f
Failed tests aren't being uploaded to swift due to the build process
exiting before the swift upload script is called. To fix this, run
the upload process as a publisher script.
We'll re-purpose the existing experimental job to test it. Thus make
the job always fail so we can then check the logs are uploaded.
Depends-on: I5ff21f544e6f2aa4bf88b7d02e65cdfb62e6faaf
Change-Id: I3f15604d8c3c2f405dc37a9d0bd4b044228e5793
The swift logs had trouble on centos hosts. To test it before switching
over on all logs again force the experimental job to run on centos.
Change-Id: I755cf7276ebbbb78dcaaa9eb1dfd33c7ddc7a11d
This repo was created from filter branching the openstack-infra/
config repo. This process brought a lot of cruft with it in the
form of directories that we no longer need. This patch removes
that cruft so we begin with a tidier repo.
Change-Id: Ibffad1b11c0c5f84eedfb0365369f60c4961a0f3