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
The update-constraints job does not need to run on the signing node, so
move it to the proposal nodes.
Update the job patterns used to decide whether to take a node offline
after a job runs to include update-constraints.
Change-Id: Ieb25446ac7a679ef26f6c09971cb2eddf41d5178
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
We have a race condition in the jobs for patches to
openstack/requirements submitted by the release jobs because the
packages are not yet on PyPI when the patch is proposed to update the
constraints file. This change moves the constraint update portion of the
release job to a separate job and schedules it to run as a dependency of
the PyPI upload job.
Change-Id: Idce73ca3813858050e8f64ece44e838266aaf5d6
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
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
Now that the tarball signing job has been proven to work for the
bindep 2.0.1 release, use it for all releases and pre-releases that
run our {name}-tarball job.
This reverts commit 1a2539a225 and
part of commit 63b56462bc.
Change-Id: I4e8564df4ec2146e6a13ffc0fc4f582b6f383f9c
Move jobs needed for pypi publishing to pypi-jobs. This allows to remove
the python-jobs job-group from all xstatic jobs.
Create new job-group openstack-server-release-jobs and add it to all
repos that use the openstack-server-release-jobs template in zuul.
Add tarball job to those few repos that specific setup in zuul.
Remove pypi-jobs from congress, designate, designate-dashboard, mistral,
sahara, sahara-extra, searchlight. These do not publish to pypi.
Remove {name}-pypi-wheel-upload completely, it's unused.
Reorder some entries in projects.yaml so that python jobs, release jobs,
publishing and translation are first.
Remove stray comment from projects.yaml
This whole change reduces the number of generated jobs from 9321 to
8526.
Change-Id: I6f5b853827e6c6a390776fe288e30befdbd571f6
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
Bandersnatch and pypi have a failure case where uploading two files to
pypi very closely to each other results in bandersnatch thinking it has
synced serial X+1 which includes both the sdist and wheel but it really
has only synced serial X. But since X+1 is what bandersnatch thinks it
has done it will never sync the actual contents of the X+1 serial (the
second file uploaded).
To make matters worse the index.html for the project is synced assuming
both artifacts at serial X+1 were synced. This means any fetches for the
second artifact fail.
We can work around this by always uploading the wheel first. Pip prefers
wheels to sdists so uploading the wheel first ensures that the wheel is
synced properly, pip will prefer it, and our jobs should continue
running.
Eventually upstream pypi and bandersnatch will need to fix this bugs
properly but this is a reasonable thing we can do locally.
Change-Id: I26062b9fefa5ce484b63e2d0ee02e0ecbe64555f
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
Monty Taylor