removing job that runs tempest tests against ec2 api.
because there are no tests in tempest for ec2/s3 now...
Change-Id: Iebc8c805b37db6a82614d00e904a34d2f369d844
With no longer setting a node default, Zuul won't pass it as a
parameter to the set_node_options() parameter function. Drop it from
the required arguments for this function.
Change-Id: I2aa8f7179ecb0bdf6bd8785653f1726321bbcb7f
Bluebox is performing maintenance soon. It would be friendliest
if nodepool wasn't asking for vms on their cloud whilst they
do their maintenance. This patch sets bluebox max_servers to 0.
Change-Id: I6e147b3e142dc185b2752f25007fca8c26d03e2d
Now that there are no jobs declaring both .*-precise and .*-trusty
nodes at the same time, it is safe to remove the associated mapping
in Zuul and let it trust that any worker registering the job name
is capable of running it sanely.
This should not be approved until manual jenkins-jobs updates have
been completed and confirmed successful on all Jenkins masters.
Change-Id: I3b40021ffbf89842ed3a53412dfffa119f311797
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
I removed a very important include from a shell script before this
experimental job merged this morning. This commit adds that line back
in so the common git parts will work as expected.
Change-Id: Id0ffd533b6c5ff459a165ff29dfd7e4fd74603d7
keystone jobs were all failing with
gate-tempest-dsvm-keystone-eventlet-full NOT_REGISTERED
This was because the jobs were running on the wrong type of node
for a devstack job.
Change-Id: Ie1e288247cf4638fe57d24896a74bcd2f0c625e3
Functional testing was introduced in in the liberty cycle (~0.7.0~3) so
testing in the kilo branch (which is capped at <0.5.0) doesn't make
sense.
Change-Id: I82fdfed33c1f752ce6fde4e3a89534f28c72b5eb
The script exits with the appropriate code depending on the result
of the test. No need to abort on any particular non-zero status.
Change-Id: Ifcdbb322edc9709c8004f1ceda2973a24b7246f0
In Ic5da694ff2daab2b958899cb0fa676dce30976f4 python-barbicanclient
switched to using gate_hook and devstack plugins, as extras.d has been
deprecated in mitaka. This broke Kilo, as the plugin support hasn't
been backported that far.
Mirror the setup from barbican to define a job that uses the old
extras.d support in Kilo and the plugin for Liberty and Mitaka.
Change-Id: I42e05f142592d77641cfa9463d47ce3216c070c0
This commit includes a job meant to be run periodically which checks
all links to assets listed in the Community App Catalog assets.yaml
file. For any dead links, an additional attribute is added to the YAML
file, and a review is submitted with the updated YAML which will
prevent the link from being displayed until it's updated with a
subsequent review.
Change-Id: I991155edca8ed92431f7a5deacf2d3938cf70ada
The requirements project runs a docs publishing post job, let's get
on it as well so that the post job runs.
Looking at current post jobs, the job fails on liberty. There's no need
to run the job on stable branches, gating and publishing
just from master is fine.
Change-Id: Icd52ed086ab7d5eb6153f9cd9257eb4a52daf728
The responding change in system-config has been reverted,
revert the change in project-config as well. Reason is that
etcd doesn't exist on all platforms.
This reverts commit 0b7f322c0b430189e969719f179da8995d6c70a8.
Change-Id: Id2c54173e37628d3ede711426b5f25ca934a5645
