The openstack-python3-jobs template has been including a py311 job
variant for some time. Make sure the same filtering is applied as to the
other python jobs.
Change-Id: I766bf197989b31af39048318b435ad31fdfb7ca0
release repository did not change to use the latest template for unit
test jobs. This patch removes the versioned template and replaces it
with the unversioned one (that was introduced with patch [1]).
[1] https://review.opendev.org/856903
Change-Id: Ie034b7bb2b1b34fa0754beafccbbcbfc178a43ea
With the latest upper constraints updating generated patch [1] the
openstack-tox-docs job started to fail, due to conflict:
ERROR: Cannot install jsonschema<4.0.0 and >=3.2.0 because these
package versions have conflicting dependencies.
The conflict is caused by:
The user requested jsonschema<4.0.0 and >=3.2.0
The user requested (constraint) jsonschema===4.7.2
This is because we have jsonschema<4.0.0 in our requirements.txt.
By uncapping the constraint the docs job is passing.
Date validation needed to be updated as well, because a deprecated
usage of validator extending method was used in the code, which was
removed [2] from jsonschema with the 4.0.0 release. This patch replaces
that with adding a TYPE_CHECKER instead.
With the new jsonschema constraint openstack-tox-py36 job does not pass
anymore, but py36 is dropped from zed anyway. That job is pulled in by
an old job template, which needs to be replaced to the new zed job
templates, too.
[1] I89576353371aa87d181610eb6242cbe961487af6
[2] d9f6384060
Closes-Bug: #1982757
Change-Id: Ida6310dd822e587ce9c424a228fdff5192ba0476
This can take a long time now with doing the final release tag
validation when all deliverables are included in one patch. Part of the
delay appears to be that pbr was updated to build release notes if reno
is present. We may look for other ways to optimize the validation jobs
to speed things up, but for now we can just make sure we have a very
large window.
Change-Id: I248968bca9a90a7b06d4d6dd0644c50d926e5f45
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
As part of retiring static.openstack.org change the publish job
to a new job that publishes to AFS.
Depends-On: https://review.opendev.org/708916
Change-Id: Ifabeb425b8398e9ccb38ef2b2cb27c1bd0454aee
Task: #37724
Story: #2006598
Switch the check-release-approval job to run on the new
release-approval pipeline (i.e. on patchset submission, then
on every comment not coming from the zuul user), rather than
on the experimental pipeline (only upon request).
Depends-On: https://review.opendev.org/706257
Change-Id: I6e0e4e9e7b44947ec5fbc9f638c05a6592d3e139
Enable the new run-on-executor check-release-approval job
(defined in project-config[1]) on the experimental pipeline.
[1] https://review.opendev.org/#/c/701982/
Change-Id: I172f5c0b4785893715e798293bb8ddd658d60b8d
We have had a bashate target in tox.ini for quite awhile, but we haven't
had a Zuul job run it on changes. Manual fixes have been needed from
time to time when someone has decided to run the linting on their own.
Rather than needing periodic cleanup, let's just have this job run on
any *.sh file changes.
Change-Id: I828715f30695fac1036b982b180a6fdaec03bc43
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Define a check-approval job that runs check_approval.py, and
enable it in the experimental pipeline for now.
As a first step the job will run as a classic tox job on a worker
node, with an aggressive 6-min timeout.
Change-Id: Iaf8ffcb691f14e83843bf2079fabaa87776f0526
This adds some zuul checks to not run jobs when only the data files have
been changed.
Change-Id: I74805f37373338d1c5763eb7d6af1d29f219e5ea
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This reverts commit e7a87665a8
which triggered the following error:
Unable to freeze job graph:
Unable to modify final job <Job tag-releases branches: None
source: opendev/base-jobs/zuul.d/jobs.yaml@master#25>
attribute timeout=3600 with variant <Job tag-releases branches: None
source: openstack/releases/.zuul.yaml@master#10>
Change-Id: I70b2e3f25cecef42ccc7a4a991c52b5a6a4765fa
Parent job is currently marked final, so attempting to override setting
here causes an error when zuul tries to load the job graph.
This reverts commit cd3ac58467.
Change-Id: Idcb8f5ceadcc36af1cceace84691e505409c6ebd
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I64903004528db07d5695f3b95a5420876ff2166a
Story: #2002586
Task: #24330
This moves the openstack-tox-py35 and openstack-tox-pep8 zuul jobs to be
defined in-repo.
Also, no need to run mnay of these jobs on patches that are only changing
documentation.
Change-Id: Ic211dabcc903dde8848c4f9be9ed9a3f8806c23a
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
The Puppet OpenStack project had a module which was not released
since 2014 and therefore it did not have an entry in the goverance
repository. The current TC chair is not available so in order to
not delay the release, set the validate job to non-voting to skip
the governance check for release.
Change-Id: Idfea40c4f3a1d624f097df34cb53d59fe25b4aaa
Related-Change: I54c4a9e9b2ec988914bc5174a599ab17ffe60cdc
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Iaffac63d47bd3c00d4512b6eac9eb53feaa79afa
Sometimes when the job succeeds we still need to review the logs.
Change-Id: I2ea1f11100a6233b13f01541f140103e224182ce
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The default is to discard logs when a job succeeds, but we need the
logs for these jobs because they are reports that reviewers use to
evaluate the releases being proposed.
Change-Id: Ibba75a547bee5a8a5e7fba76b5962c0382009bb2
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
We had previously installed our docs dependencies as extras in
setup.cfg. Doc jobs are now changed to not install the project,
so these dependencies are no longer being installed.
With recent changes to the doc jobs, we need to specificy that python3
is used. Update the zuul config file for this.
Change-Id: Ie925efefb1126dbe7fa0a9f0f1727da01f48c512
Depends-on: Ib882a4d09898ff206b36ac8aef840bee0748368e
The py35 and pep8 jobs are defined as part of the CTI and as such
should be managed through the project-config repository. Removing the
entries here should also fix the way the exclusion rules for files
that don't affect the tests are applied.
Depends-On: Iaa8dc88e999d22e2242eeb963838b29ba35ac3aa
Change-Id: I1dd45d269716d54c8d56a12912676bdc269aafcb
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Előd Illés