Now that bandersnatch is running in parallel, go ahead and stop
building the pypi-mirror based mirror.
Change-Id: If5935b356e222c2f4d474a2cec8add3cc66b6010
Solum is currently not compatible with Trusty's rabbitmq. While solum
debugs this run their devstack tests on Fedora 20 and run the test on
Trusty as non voting so that the issue can be debugged.
Change-Id: I5b9454c0e22e9a07492dacb0ce8c17b9584dcae5
Not every zuul changeish has a branch. As a result we must check that
the object has a branch attribute before accessing it. The code
previously attempted to do this but due to precedence rules the binding
of the check was wrong and insufficient. Fix this with liberal use of
()s to make the precedence explicit and correct.
Change-Id: I06b3fd7ec4e5bdd14af3bc0bb1f7da39e238a879
The zuul node label selection functions missed a few corner cases where
precise, centos6, or trusty needed to be selected. Specifically if the
job name includes precise that job should run on precise. If the job
name says centos6 that job should run on centos6 and so on.
Change-Id: If9a99c0347412c8bb54dd663dbdca4908cb3eb03
This reverts commit 72c32e161e126a7dfdda82f801ba4c18b2f76a9e.
Jenkins masters have all had their gearman plugin updating which makes
them register jobs properly.
Change-Id: I6894e590a2ee033ad46149c2859b8f8c33055c5a
This reverts commit c76f930c09b57ac134d8610ed5fde6d3b802806b.
This is necessary as there is a Jenkings gearman-plugin bug that causes
a node to register all available labels for a job even if it is capable
of serving only one label. This bug prevents zuul from properly
selectiong nodes as desired by this change.
Change-Id: I035d31a91c4ca1a8366316b7ff422f4a2b03622c
We have trusty slaves, we have trusty workers registered in gearman,
make zuul use them for everything newer than icehouse when running dsvm
jobs.
Change-Id: Iae037e6c1853aee5044c8e8549d8b6dc93db2b02
In order to facilitate the transition from precise to trusty for Juno
testing we need to make zuul the decider of node labels for every job.
Do this by refactoring how we apply parameter functions to zuul jobs.
Since we can have only one parameter function per job it is easier to do
decision logic in a single global parameter function. Add this single
function and have it maintain backward compatbility with old parameter
function selections. But also make it select the ZUUL_NODE for every
job.
Change-Id: I42fa26fc42c7dc4e94d3a7382cc8de0a5e6d1f36
* doc/source/jjb.rst
* doc/source/stackforge.rst: Update examples to recommend
bare-precise nodes in new job configuration.
* modules/openstack_project/files/jenkins_job_builder/config/*.yaml:
Change the node label for all jobs opreviously using precise to use
bare-precise instead.
* modules/openstack_project/files/zuul/layout.yaml: Get rid of the
transitional matches for setting the single use parameter function
on specific job names and just set it on everything as a default.
Add patterns for jobs which need long-running slaves to apply a
reusable node parameter function instead.
* modules/openstack_project/files/zuul/openstack_functions.py: Add a
parameter function for reusable nodes which refrains from enabling
auto-offline behavior.
* modules/openstack_project/templates/nodepool/nodepool.yaml.erb:
Double the minimum ready bare-precise nodes to accommodate
additional load.
Change-Id: I2a90c5b120a50bb8033c891702185f054ee84d35
* modules/openstack_project/files/zuul/openstack_functions.py: Update
single use function to select rackspace for tempest check tests.
Change-Id: I9f930dbddb2284e6c5a9672f454456b98953967a
Use the new gearman-plugin single-use feature with all 'devstack-vm'
jobs. This is compatible with the current devstack-gate scripts,
though once this is in place, they can be updated so that they no
longer perform relabel operations.
This is also compatible with future devstack-gate nodepool operations.
Change-Id: I6fcadb47ba5eeead3d11926019b3c041305c95f7
This calculates the full LOG_PATH in the Zuul config and pases it
to Jenkins. The new path is similar to the old but with the
substitution of a short ZUUL_UUID at the end instead of the Jenkins
build number in order to avoid collisions from multiple Jenkins
masters.
Periodic jobs add a node name to their log path to avoid collisions
from multiple masters. Unfortunately, that value is not accessible
to the logstash worker. This can be solved by having Zuul trigger
periodic jobs.
Add the ZUUL_REF to logstash as "build_ref".
Requires https://review.openstack.org/#/c/39130/
Change-Id: I40bad59e3ad8ed6b4706762ed8b833fd15c13b0d
And use that when constructing log paths and URLs. Use a substr
of the change id or commit sha when constructing URLs so the log
directories are deeper.
Make copying the test results a macro (it's used in several places).
Update the gearman log client to take advantage of the new parameter.
Requires https://review.openstack.org/#/c/36304/
Change-Id: I64faa35eddc4105271efa3de4f83b608b77655c2
Those branches are closed, so remove all special configuration:
* ACLs
* Bitrot jobs
* Manuals jobs (which weren't actually being triggered anyway)
* Zuul branch configuration
* Zuul job functions.
But leave the now-unused openstack_functions.py file in place
so that it is easy to add in a custom Zuul parameter function
in the future.
Change-Id: Ib0732753543aff0b1de5880fbe8aadc4f8616835
Reviewed-on: https://review.openstack.org/28323
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Approved: Jeremy Stanley <fungi@yuggoth.org>
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Tested-by: Jenkins
The job name matched the python27 functions regex, but as a post job,
it has no change/branch object. Make the function safe for post jobs.
Configure them to also be triggerable by zuul (the timer still works
because all zuul variables are ignored).
Configure them to not run concurrently (there's only one matching
executor so it shouldn't be a problem, but be explicit) since they
share an output location.
Change-Id: I210da46bac1a8fa5ac9a931f07f189b3734b2ab0
Reviewed-on: https://review.openstack.org/25646
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Approved: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
For all python27 jobs, use oneiric slaves if the branch is
stable/diablo. Python26 jobs are already on oneiric due to
lack of python 2.6 on anything later.
Change-Id: Id440e14721ccdd4225c5e5b170510c3c000a36b3
