Change https://review.opendev.org/737995 failed the promote job
openafs-rpm-package-build-promote since the gate job was not run.
Add a files sections, so that the promote job is triggered when the gate
job is.
Change-Id: I2f45d822d1f1301c406799f5dd7a4a1a44f26f0c
OpenStack now uses python templates per release, like
openstack-python3-victoria-jobs.
Some projects need more fine granular control over which jobs to test,
so use:
- openstack-python38-jobs which just adds py38; this follows the pattern
with earlier versions
- openstack-python38-jobs-no-constraints: Same jobs but without
constraints
- openstack-python36-jobs-no-constraints: Same jobs for py36
- openstack-pep-publish-jobs to run pep8 and publishing of tarballs
Update templates openstack-python35-jobs-no-constraints and
openstack-python37-jobs-no-constraints to follow the scheme above.
If this gets approved, I'll review users of
openstack-python35-jobs-no-constraints and
openstack-python37-jobs-no-constraints and add
openstack-pep-publish-jobs-no-constraints to their Zuul configuration
wherever needed.
See also https://etherpad.opendev.org/p/-CBx0IaMT37oFBHdt8iV
Change-Id: If5ce06f620f5cd2161b752e1cc402a4e39d36e90
We should not be using this on master. Also update it to pin to
python2 to get ready for zuul-jobs changing the default for
sphinx to python3.
Update descriptions to make clear that rocky was the last release
this is supported.
Change-Id: Ib896713623f58a8164d1a2e5f49dc5d316e292b9
uwsgi broke installation from source with their latest release [0].
Since we want to move away from source installation anyway, make
grenade based jobs non-voting for the moment so that we can backport
[1] properly.
[0] https://bugs.launchpad.net/bugs/1883468
[1] https://review.opendev.org/577955
Change-Id: I3891e4eda3c459acefa0d3c028cda649b984ff0c
Related-Bug: 1883468
As the zuul manual says
If a child job inherits from a parent which defines a pre and post
playbook, then the pre and post playbooks it inherits from the
parent job will run only with the roles that were defined on the
parent.
This is to stop role inheritance altering the parent job. So include
the system-config roles here.
Change-Id: I9e5c0d128e5669e5354c5568bdbc00a3aa27e95b
The extant roles are not really right. They run in periodic and poll
tarballs to see if they should build anything. They are not gate
tested. I do not know why I did it like this; but it was a long time
ago.
We should have roles that build in the check gate, and upload only
when the client version changes.
Additionally, I found that the upstream .srpm we were building from is
not quite right; it won't build on ARM64 for example due to the way
it's autoconf machinery has been generated. The best way is to build
your own srpm from the upstream source using the method linked in this
change.
This builds and publishes artifacts for centos7 x86 and centos8
arm64/x86. A follow-on will publish these.
Change-Id: Iefb01ba48a457388bb5412ddad3d7dafb00d620c
Revert part of I69254919958cec67095b25724b417282e1f270f8, bindep.txt in
requirements is used for generate-constraints as well, a special wheel
profile does not help. Use the default profile, like we use for
generate-constraints as part of proposal job.
Change-Id: I229e06579849c9fffa00ef33aa94d730331110d3
These jobs needed a change to bindep.txt in requirements repo to pass.
Depends-On: https://review.opendev.org/731728
Change-Id: Ibda2d0082c18d08f59e646f7a061232fd8821bf0
Run the wheel build jobs if we update the build roles or playbook.
Add build-wheel-cache-debian-buster only in followup since it does not
pass yet.
Use bindep.txt from requirements repo for this, use both test and wheel
bindep profiles.
Change-Id: I69254919958cec67095b25724b417282e1f270f8
Remove the job restriction so we can run these jobs in this gate when
we update the roles/playbooks. The restriction is moved to the
publish job with the dependent change.
Add dependency on requirements so it is available outside that
repository.
The system-config roles aren't required. I think this was from when
we used to directly copy to afs from the build nodes and required the
openafs-client install roles. Now the executor copies the results via
the publish jobs.
Depends-On: https://review.opendev.org/731632
Change-Id: Ica59634eec533db20fe8b1dd148ee9b4d041fd3c
Move the wheel build jobs out of project config so we can run
speculative testing (project-config is a protected repo).
requirements project has these jobs in it's gate.
The only change here is they are renamed to "wheel-cache" from
"wheel-mirror"; both to not conflict but also I think cache describes
what it does a bit better -- we put the cache on the mirror but we're
not mirroring something created externally.
See-Also: https://review.opendev.org/731401
Change-Id: Ib41607c4842dccf27b711947bf356ef5d74a1059
commit 202cce830e4e0d63684fefc74dfc8d6aaa9248c6 introduced
new npm jobs. npm jobs on ubuntu-xenial do not work now
as yarn does not work with nodejs <10, so I believe this change
has no negative impact. It is required to fix horizon jobs
in stable/rocky or older.
Change-Id: Ie51711e05e323aebaab67f766eb7189fb16fd322
We transitioned from Gerrit-wide replication to using repo-specific
jobs for Github mirroring of official OpenStack repositories.
The job was only triggered by merges ('post' pipeline), which means
that new tags are not replicated until the next merge.
Since that can take a while for less-active projects, we should
also trigger that job when a tag is pushed ('pre-release' and
'release' pipelines).
Change-Id: Icfb5d4053b59074c5fc5a366557b71aec4039c1d
The dependency changes the test job, update the change so
that we get the new job with browser.
Depends-On: https://review.opendev.org/727231
Change-Id: I2eb13c2eaf51dd4fc8a8dadebc55971bdc3d4f58
'grenade-py3' is switched to new grenade zuulv3 native job,
we need to switch integrated-gate-py3 template to use the new
job name so that projects using this template can start
running the new job.
Details:
- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014602.html
Change-Id: I333e8e066c6e225569b21e2450ccbaa2e588c232
Add a project template for jobs attached to official and active
OpenStack repositories (like the GitHub mirroring).
Change-Id: I1004508c66d53a5e3c11af1e3dbf411338cfd25f
Add the stable/ussuri branch to the list of branch for the
periodic stable job templates.
Depends-On: https://review.opendev.org/#/c/723605/
Change-Id: I5d671b0776b150de8eb730469e06b1106fa5127e
These moved to system-config so that unwinding them can be more
self-contained. Remove them.
Depends-On: https://review.opendev.org/720889
Change-Id: Id0959976b2a6e51e3d62f851bc5866f8980e8269
python-charm-jobs template is for py2.7 testing which
was used by various charm repos and they stable branch.
Those repo moved to py3 template but stable branch still
need to keep using the py2 template so let's update the
description of this template.
Change-Id: Ic17ec65b2229d46b799e0c41824e6e368723098b
pylint is notoriously noisy. Let's not bother people with its
comments.
Depends-On: https://review.opendev.org/716599
Change-Id: I9443f202defed25fd418e0d0a42bf8413f54310d
This job ran on centos-7 which are are no longer testing. That means the
job can be removed.
Depends-On: https://review.opendev.org/715034
Change-Id: I2fdd01217d38bc73d241460359a9ce2e7d6b1687
The apply test does not test anything related to docker or ansible.
Stop running it on docker and ansible related changes.
Change-Id: I1a6e183d1bc9349cb400a087d3640a185b76b950
Remove the now unused jobs legacy-puppet-httpd-forge-upload and
legacy-puppet-storyboard-forge-upload.
Also, remove parent legacy-puppet-openstack-integration, it's not used
anymore.
Depends-On: https://review.opendev.org/710110
Change-Id: I6998d80228fd16911b660aa04f40e710bae1df99
This is part of step 2 for retiring the x/devstack-plugin-bdd repo.
Depends-on: https://review.opendev.org/710062
Change-Id: I4323bdc788caa807d0f1cac654560b1d4450eae9
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
release-notes-jobs project-template used in stable branches like rocky
uses python2, but it refers to the master branch of the requirements repo
which now supports only python3. As a result build-openstack-releasenotes
job fail. The releasenotes build is always run against the master branch,
so we can use python3 in release-notes-jobs project-template.
release-notes-jobs and release-notes-jobs-python3 are now similar,
but it would be good to keep both as release-notes-jobs is referred
in stable branches in many repositories.
Change-Id: I708b20424a7b044cac3ea589714235fce5fae546