Sadly our fedora names are not constent yet :(
Change-Id: I9fa840975b2f3136e9d52dae352f33e692296694
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
The tripleo-ci jobs were using a regex that just looked for
*-tripleo* in the job name, which also matches tripleo-common and
python-tripleoclient. This causes the py34 jobs for those projects
to sometimes get scheduled to precise nodes that don't have a py34
interpreter installed.
This changes the tripleo-ci jobs to be named tripleo-ci-* and
updates the regex appropriately so it will no longer match non-toci
jobs.
Change-Id: Ie4d803574221b936b249673436db36fd75940587
We need to be explicit that we want the npm upload job to run on the
release slave otherwise gearman will attempt to run it on the default
slave label which will fail because that job won't be registered.
To do this rename the job so that it matches existing convention which
makes the regex easier to read/write. Then update the reuseable slave
regex to include the job which will force it to run on release slave
without offlining the slave.
Change-Id: I26355680f2d8fc3fa5f514370d1586deb701c21c
Add fedora 22 node matching to openstack_functions.py. Although we
could make the re even less specific, I think it's best to just match
on what we have.
This is my own silly fault for not noticing this in
I2be12566985ac992a2da0c8174b4c9064347d91f
Change-Id: I98eecf21b8cee5114ffccef4d23384a4c4cc6774
Enhance regex to handle the translation liberty jobs like
nova-propose-translation-update-liberty.
Change-Id: I592443baa981b44437e09209b933f69a45a85b7c
Now that the Zanata translation jobs have had their -zanata suffix
removed, we no longer need this section of the regex to force the
jobs onto the proposal slave.
This reverts commit e1cdfc4a42450e01d40b2eed5b63ae5e4a0a76ad.
Change-Id: I6be79c60b480f21904312289c5f00f88c3a956d6
The jobs did not run on the proposal node since the regex did not catch
them. Enhance the proposal re.
Change-Id: I12fe718f0fb82d7036a0fe0c7e0233e16ebc8173
In Id3f6175fcdd4a21019eabca56cd337145ff9c2b0 os-ansible-deployment moved
into the openstack namespace and was renamed to
openstack/openstack-ansible. It's specs repository will also be renamed
to openstack/openstack-ansible-specs.
This also switches the publishing of documentation from readthedocs to
docs.openstack.org and includes both doc and spec publishing.
Change-Id: I10588f1118f21793ef9a1a647184cf2e8de07260
This patch adds an ubuntu-trusty node-based non-voting
check to os-ansible-deployment to help determine whether
the differing images between hpcloud and raxcloud are
contributing to the gate check failures seen solely in
hpcloud.
The idea is to use the exact same image across both
clouds to see the results.
Change-Id: I7809e3f4b3012586f4aaa0de9d9bc7b0011e720d
Since we have zuul picking node labels to accomodate for possible branch
specific label needs we need to whitelist the kolla image build jobs as
they always have a single build_host:image_type mapping and branches
don't affect that.
Change-Id: I75e20a53c2091df1571eeff89cb6fd2e927e0a91
Our RTFD hook just does a curl request to upstream. As such, it is
very expensive to nodepool to build a node for the purpose of just
using curl.
Lets move the job to use the proposal node which is long living.
Change-Id: I8f407fdaeb890a4ae6a9b99caefe836b8f2f7819
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
We're really close on the ubuntu-trusty images. Add in an experimental
job so that we can verify before re-switching all the multi-node stuff.
Change-Id: I5311fb8b67abb644435033f2a88ea3dd9453d87f
This reverts commit 2b5b800d4fc48724da66e72e03812222125d3667. These new
images cannot be reliably uploaded to rackspace which makes iterating on
image updates/fixes very difficult. Switch back to the old image (using
new shorter hostnames) to get multinode working again. We can switch
back when we have uploads sorted out.
Change-Id: I46e051a4a566ae400c2fc153ad72596c853af32c
Because we want to move to it anyway, and it lets us fix the hostname
problem with glean.
Depends-On: I67ea62ebf9360f72f121d77acd1cbd35d8db728b
Change-Id: Iabe8b0f0cac9d80180b9542263ade5ffdfe641a2
This job doesn't have "dsvm" in the name, so zuul is calling
default_params_trusty() on it rather than devstack-params(). Correct
the functions to match this expectation.
Change-Id: I25e0e638d3d0dc1be66dfc8e17712ca995aa3a3a
Update the experimental nova Python 2.7 unit test job which runs on
thin "ubuntu-trusty" workers to use bindep for determining its
distro package dependencies, and rename it to something more
appropriate now that it's not actually using devstack-trusty workers
any longer. Also switch it from gerrit-git-prep to the new
zuul-git-prep builder macro, and while at it adjust zuul-git-prep to
have a zuul-branch-git-prep variant rather than requiring a branch
parameter for the more common case.
Change-Id: Ib3f4844c1203f8a3890d9e5d91347d4507b5d08b
This is mainly cleanup to get rid of the old misleading slave label.
The old worker already has the new label applied, to make switching
more seamless.
Change-Id: Iefd6ed3fbb696b2009e8525c4cac1f0e1aca50e3
The new nodes are running in both HP and Rackspace now, so it's time to
make sure that they can run devstack.
Change-Id: I77704f2a3ce79851df677d2c38cd7ad504427a97
Update the zuul parameter function so that the
propose-requirements-constraints-.* jobs run on
proposal.slave.openstack.org instead of the default bare-trusty
nodepool nodes.
Change-Id: I855ae0fce9fc8cb5efc1fc29ec354f8e0f7f8156
This was missed since it relied on default-equivalent behavior until
we switched the node type for the project yesterday.
Change-Id: Id3f75916f28c8a655c5bb89fee58c22d6f5c991a
Co-Authored-By: Jens Rosenboom <j.rosenboom@x-ion.de>
aiopcpu is an exceptionally cryptic name that doesn't mean anything to
most people reading test results. multinode is what the job is, and is
much more understandable at first glance.
This changes the naming from aiopcpu => multinode. Should we create a
different kind of multinode test in the future, we can come up with an
appropriate name for it then.
This is safe to change because the devstack-gate logic actually is
fully != 'aio', not == 'aiopcpu'.
Change-Id: Ic7fe31a397af8a14ecf33a4902908ff9c03d11d3
With the dependent change merged, we do not have f20 nodes. I could
not see any other Fedora 20 specific work-arounds in any other
scripts.
Change-Id: I7c147f0c1cad1b1eaf22c70ec26c47983a00abaa
Depends-On: I435f0d95dbe7f5d8e90c1fe8368dd42ebb241c88
In I97362b1cc6a8c19b54903e53638aba8cb4928e19 an extra '/' was removed
from most instances of BASE_LOG_PATH, except for ones generated for
changes in periodic pipelines. Add the missing '/' in that case.
Change-Id: Ibd99b88651d5cc3a7627fd4843a9a24f9be68464
Add a job that will propose a change (or update a change) to
normalize projects.yaml, and run it once daily. Normalization,
in this case, chiefly means removing un-used upstream lines
from projects.yaml (but will also catch minor YAML errors and
line wrapping).
Also simplify the proposal node regex.
Change-Id: I6520dfcd6f523886aba352f9bd7f9186cfeed84a
These are no longer being used to run jobs, so clean up references
to them.
Change-Id: Iac7ffde66a2d5d1a1361ed9bcadb9144e034f10f
Depends-On: I40d5d09f28ef53583d239d2e852e9c50b5962cf8
Add an experimental devstack f21 job as the first step in bringing up
Fedora 21.
As requested condense this into a job-template for the fedora jobs.
Also add the node matching update; this is kept as a separate regex to
help it show up when grepping.
Change-Id: If084c2cbf058c9adbe0cb706559711a9f3959aa4
Depends-on: If764f676f43c86830b4277adaaf71098e9d4140b
Logs are currently coming back from zuul with two slashes in them.
The paths already have a trailing slash so the final LOG_PATH doesn't
need to add it.
Change-Id: I97362b1cc6a8c19b54903e53638aba8cb4928e19
zuul sets the path for where logs are stored. In all our cases this
is a folder containing the console.log and other assets. We should
denote this is a folder by leaving a trailing slash. This also means
that os-loganalyze can determine if it should load an index.html
faster by looking for a trailing slash.
Change-Id: Ia1de627c01ee43c461d25b184fb61cbfd91fb19d
Puppet module lint and syntax tests should also be run on trusty along
with unit tests. This patch adds lint and syntax tests to the regex to
skip assigning stable/icehouse branch tests to trusty nodes.
Change-Id: Id7f091678f0140f0d4feb9c317d653ac79b43d58
Without this patch, stable/icehouse branches in stackforge/puppet-*
will run unit tests on Ubuntu Precise. This is a problem because the
version of Ruby and therefore Facter is too old on Precise and causes
failures for certain Facter values only available in Facter > 2. This
patch removes precise from the nodes to test the puppet-* modules on
and adds the puppet unit tests as an exception to set_node_options() to
prevent zuul from trying to use precise on stable/icehouse.
Change-Id: Id7453171a8ca2321528e0e0d3d2a0984e0304db3
Next step in migrating to dib is moving to devstack-precise-dib images
in hpcloud. We have images and slaves built with dib for this label now
we need to run tests on those nodes. Add experimental jobs to
devstack-gate for nova network and neutron run against icehouse on these
new -dib images.
Change-Id: I3efb17d93173091827623c15704e5a79be8fca33
The last Havana stable point release, 2013.2.4, has come and gone.
As it is no longer under support by the vulnerability management
team and stable branch maintainers, remove testing for it. Note that
this also means ceasing grenade jobs for stable/icehouse changes,
since they begin by deploying stable/havana.
Change-Id: Idac2f43d19dff78c3b0ff3c155f3835cafac446e
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
