This commit is part of a series to retire the Packaging Deb project.
Step 3 is to set the Gerrit ACLs for these repositories to
read-only, remove them from CI configuration and IRC bots (as in
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project).
Change-Id: I05c9e4a37ecb1eefe1909be3cb5fa56ee10710ff
Across the entirety of our job config corpus, we only ever set the
tarball-site parameter to tarballs.openstack.org. Instead just set
it directly in the publishers where it's needed and reduce
unwarranted confusion for people writing job configs. This also
allows us to get rid of the parameterized sites in the tarball,
wheel and war publishers.
Change-Id: I31109f41177b8c07177d7ed8ef16cbfd135131ef
I'd like to play with the Gerrit API with curl with an existing
gerrit repository. Please allow me to train before going live.
Change-Id: If7ecca00032e075f39cb9d3552152836136b7405
* Add jobs for dev zuul-launcher which will run on zuul-dev.o.o
* Update dev zuul layout with same pipelines defined in prod layout.
* Setup zuul-dev layout to trigger on review-dev projects.
Change-Id: Ief59c0b52b196b614f8a7da859c3ba024813f1a3
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
There are no jobs called icehouse-dibtest anymore, remove special
handling from openstack_functions.
Change-Id: Id8bf7929af54b3a122766aaf6b391766a9d983d7
zuul-dev is for testing only so we set all zuul-dev pipelines
to low priority. We also want to update zuul-dev pipelines
to match zuul pipeline configurations.
Change-Id: I392496d2d48952fe2eac24e1ebcdf1aea0721e06
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 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
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
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
Add a project specifically to make it easier to test that
jobs are executed on the periodic pipeline.
Change-Id: I08eec31a701fc9d6cbd79bdc38e065a2d5ac2593
Direct zuul to run gate-noop jobs on jenkins-dev.o.o so that we can test
the full workflow of review-dev <-> zuul-dev <-> jenkins-dev.
Change-Id: I8b6c8d85a4892525bd9726d1ae7d56c952ab0cae
The zuul.o.o layout.yaml file references an openstack_functions.py
This change duplicates that for zuul-dev.o.o. To do that zuul-dev.o.o
needs it's own openstack_functions.py file.
Change-Id: Ifb8bb921545f4ab4557e02c676c85ced20687ba3
Zuul barfed reading the layout file because of the extra space.
Error from zuul:
yaml.scanner.ScannerError: mapping values are not allowed here
in "etc/zuul/layout/layout.yaml", line 22, column 28
Change-Id: Icaf2d5aa5904907c441d377ccafdd107f4d9d77e
The build and test jobs were no longer running for events from review-dev.o.o
This change updates the dev zuul layout file to match the production one
so that zuul-dev will hopefully trigger on events from review-dev.
Change-Id: I6c9b918c178deae4b17f590e8d0d40edc4e9fb28
Replace URLs for workflow documentation to appropriate parts of the
OpenStack Project Infrastructure Manual.
Change-Id: I468ae38021b4b55fea84179abe866ddd9e845fe0
We've had some cargo culting of the access "refs/meta/config"
stanza, so let's remove it where it exists.
A follow-up patch will consolidate all puppet-* module acls into
a single acl that also has this fix once change
I1837cef4610d23406d34b15cc949df62a616d960 merges.
Change-Id: Idde43c5b0ed49649e41bb9c9ee699ae8824fb068
The status quo is that the files are the same. They probably
should not be, but we can change that in a later change.
Change-Id: I78322202235ce6a1dd6487c5debde1ad1dd546ae
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