The devstack unittests source stackrc which will fail if there is an IP
conflict with cloud networking and the default safe ip address range in
devstack. Avoid this issue by setting the value we set in d-g runs.
Change-Id: I66eb221f2ae4bb39e8e21d0e644df4ec4682dc92
Remove branch-git-prep, we can use zuul-cloner everywhere.
Rework zuul-git-branch-prep to follow the logic of
zuul-git-branch-prep-upper-constraints. Note that zuul-git-branch-prep was not
used prior to this patch.
Change occurences of branch-git-prep to zuul-git-branch-prep.
Change-Id: Id938a858a0ff1967b97293405ef41b9b281f407f
We do not need gerrit-git-prep anymore, zuul-git-prep works on all our
slaves and has the advantage of using zuul-cloner so that the local
cache is used and Depends-On works.
Remove gerrit-git-prep and use zuul-git-prep instead everywhere.
Change-Id: I2f106af58f78fceaf3c497fe43e6f5a002695645
So we can avoid using the jenkins-specific postbuildscript plugin,
move the proposal slave cleanup to a builder. Run it first so that
it always runs. Since we're running it first, we can't use it to
clean up our current workspace, so instead, ask it to clean up all
workspaces.
Change-Id: I54a187d643fb76f10cc11411d546c41348b5592e
We have some headroom on the logs filesystem and this allows us to go
back to more reliable methods of grabbing logs. Specifically we are not
required to have http access back to the jenkins master from every job
that runs into order to get the console logs then upload them to swift.
Change-Id: Ie8479c224b2fd3c3efca4e1bf4157656540eccff
slave-cleanup cleans up more than 100 MB for each job it runs - and it
cleans the same content that we normally clean when starting the job.
so, this will save some space on the proposal slave.
Add the slave-cleanup run to all jobs running on proposal node.
Change-Id: Ide862b0d1d066adbf992de7f542be2d4d20cf9b1
Devstack used to be using "shocco" to build HTML pages of scripts,
which I think was the reason these jobs were not using the existing
framework. That is removed with
Ie7f4b265368f1d10a8908d75e11d625b2cc39e7c so I think we can remove any
devstack-specific documentation jobs.
Change-Id: I3a4128f6ee24b295e86d9e13af1e6d0a4d429269
Use the existing "install_prereqs.sh" script to install the packages
from the "general" package list, which might be required to run
unit-tests. Do this before we revoke sudo so that we can still run
the unit-tests unprivileged.
Change-Id: Ib47d802a31a0f4c2a49daa7e6698e37c70a2365a
Related-Change: I77c8c2019fb8b8174cdfaed3e56ebf728f0732b7
Though branch-git-prep handles ZUUL_REF not being set, propose_update.sh
does not. We thus set ZUUL_REF to master.
Change-Id: Ie2dd25e312d0a7f56bc8b7eac27cfe0c41b9041a
This is intended to obviate I72e769e5479f651673ef24b4ee20f92b12049f74
Change-Id: Ifef7573acb00ad5fb03859f737f4cb96043392f2
Depends-On: Ia04ab72900c8efd5d5289fbd7632201dcaa3e5d9
Between the Icehouse and Juno releases, OpenStack changed its
supported Ubuntu LTS platform from Precise to Trusty. In support of
continuing testing stable/icehouse and prior branches on Precise
while starting to test newer branches on Trusty, a branch-based
decision tree was introduced into our Zuul configuration by way of
complex parameter functions with an ever growing list of regular
expression matches on job names.
Now that Icehouse is EOL (in fact, Juno is too) this simply adds
unnecessary complexity and an attractive nuisance for cargo-cult
copying into new job and job-template definitions which don't even
need it. In preparation to remove the associated parameter
functions, get rid of multiple labels in all jobs and set them to
whatever label Zuul would ultimately select.
This change touches a vast number, possibly a majority, of our jobs
and so manual jenkins-jobs updates on all Jenkins masters will be
needed after this merges, before it's safe to approve the
corresponding Zuul configuration cleanup.
Change-Id: Ic952ee02da2c77fe2ace81c4e2fa87531be6119c
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
Fix wrong path, it should be doc/build/html - as it is
already in the source variable.
Fix setting for node, this is a job, not a template.
Change-Id: I6a55f9c090a046f6e85df79ea8c8291354be9f0d
Publish devstack documents in a post job on
docs.openstack.org/developer/devstack
Also, add a check job (non-voting for now).
We need extra jobs since devstack does not support the
build_sphinx target.
This depends on these two patches for devstack:
* https://review.openstack.org/126714
* https://review.openstack.org/126720
Change-Id: I68f85e13848af0bc25a101ae7474ce9fb240393f
Monty Taylor