This commit defines the nodejs v20 job template so that horizon
and all its plugins can use this template to run nodejs jobs with
nodejs v20 which is the testing runtime for 2024.1 release[1].
[1] https://review.opendev.org/c/openstack/governance/+/900224
Change-Id: I47a89078dd70da58f95c09eea23ec00a69b5b268
There are three job definitions here for testing
neutron with the master branches of other projects,
specifically neutron-lib, oslo, and ovsdbapp. As
neutron is no longer testing py310 in its master
gate, create py311 versions of these jobs so we
can move forward.
Also changed the periodic jobs here to start using
the py311 versions.
Change-Id: I28e1d41ebd36fbbe9ed3e4c18dd9604a906af043
Enable py311 unit tests for master branch only and run py38/py310
for stable/2023.1 and stable/2023.2 branches.
We found that we have an issue running py311 tests on debian,
and have decided to fix it in master branches only.
Change-Id: I52801caecab3db55b80e041b778a5a6cbaea9af8
2024.1 cycle is going to start and we are defining
testing runtime (depends-on). This commit modifies
python job templatefor the same.
Note: this makes py3.9 and py3.10 job to run on master
periodicly (not on every change) with assumption that
running py3.8 and py3.11 jobs should be enough coverage
to run on every change and able to catch anything break
on py3.9 and py3.10 too.
Depends-On: https://review.opendev.org/c/openstack/governance/+/891225
Change-Id: Ie2b56bac8465ab6847168a09ac60c9d96d7c23e7
neutron-grenade job definition is gone with neutron
stable/train is EOL but it is used in integrated-gate
template.
This fixes the zuul config error for neutron-grenade job.
Change-Id: Icad45cc966cbe81273a5be9311ab17c1b653f3e1
Remove the template, it is not used anymore.
The pypy job is still used on older stable branches.
The nonvoting template is also used on older stable branches.
Change-Id: Ib44e719ca341e1a9f8a0080f92032d752519f3a4
Python regexes are deprecated in Zuul, so update the use of regexes
in branch matchers with re2-compatible syntax.
Change-Id: I2216976a9c040cdf1d324f90831a543f7cf4a15d
Nodepool now requires Python 3.11 and so cannot be installed with
the default Python on our default nodeset. Specify a debian-bookworm
nodeset where this version of Python is the default.
Change-Id: I961430b678c3d126a2808320a8529d8649d879ac
We are near to the release of 2023.2 and release team
is starting to create the stable/2023.2 (for lib) soon.
To continue testing the same set of job (py3.9 and py3.11
n-v tox jobs, this change adds the stable/2023.2 in branch
variant for applicable jobs for 2023.2 release.
This way any early cut stable/2023.2 as well as for projects
still have master for stable/2023.2 will continue testing the
same set of jobs we do during 2023.2 release (current master).
Change-Id: I53134ef9b57e9434b8916e4fd146010074d88d59
Python3.11 is default in Debian 12 and which is going to be
mandatory testing in future cycle. It is good to test it
as non voting in this cycle so that projects will get time
to fix the things in advance.
Change-Id: I8c74a3f21b8696389d692c7b0706cfe6f43120f8
Projects ocata branches have transitioned to End of Life, which means
that all ocata related branch filters and unnecessary definitions can
be removed.
Change-Id: I6bae6ce07c58855379db7afd9394b94de3781fee
All the project that had periodic-stable-jobs template set in their
stable/rocky branch have transitioned to End of Life, and their
branches were deleted [1]. This patch removes stable/rocky from the
template as it is not needed anymore.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031922.html
Change-Id: I74c3a368fccedd4c1c023699535d5dcc7c00923c
Some projects want to include python3.11 in their testing, provide a
generic job for that like we have for older python versions.
Change-Id: I725b94bee6601a81b5e64db204bf3488674eff9d
Increase the timeout for building a snap to 60 minutes; with some
of the transient changes in the Python dependency chain the snaps
have to build quite a few more native extensions, pushing out the
build time.
Change-Id: Icd7f2e10522c2cf69107db74823bf8b767a9e53d
Changes to the normalize_acl.py script should be self-testing so
that we don't break the project-config-gerrit job.
Change-Id: Ib42ee415d39f0239a8ea62c9c3d39b3f215a9ae4
Since Zuul 4.7.0:
> The following attributes are now ignored:
>
> * The ``report-build-page`` tenant configuration setting.
> * The ``success-url`` job attribute.
> * The ``failure-url`` job attribute.
Remove `success-url` from all jobs.
Change-Id: I1379221d47edefff716875d801bedf8eee067314
2023.2 tetsing runtime is defined(depends-on), this
prepare the job template for the same. As we use the
generic template for master as well stable release testing,
this modify to add the py39 job for master (2023.2) and run
py38 only for stable/2023.1.
Depends-On: https://review.opendev.org/c/openstack/governance/+/872232
Change-Id: I5579fd0f86105fbf5f4c6875bec5996a3f6fca6e
Stable branches of some projects (Glance, for instance) use Python2.7
for their functional tests. Pre-install Python2 packages for these
stable branches.
Change-Id: Id629fb84ab64db136b12f6e36dfd7aed1c593cd6
Recently openstack-tox-py310-with-oslo-master jobs started to fail
with "No package matching 'python' is available", due to that [1]
dropped py2 from nodepool images, and the base job's parent is
openstack-tox-py27.
[1]: https://review.opendev.org/c/openstack/project-config/+/872476
Change-Id: If66af5320d9a208035d9d1ea219eae7d87a31072
As noted inline, we dropped the install from the base images. This
should pre-install python2/-dev to return us to about the same state,
but just for the legacy jobs.
Change-Id: Ia8cf6911cb48dfbef59fcf890d4b29d162dc11ad
There are two problems we need to solve when enabling FIPS for
multinode Ubuntu jobs.
1. Ubuntu nodes require a subscription to be activated with a
subscription key that is stored as a secret in project-config.
2. Because enabling FIPS requires a reboot, we need to execute the
enable-fips playbook before the multinode playbook. If not,
resources set up by the multinode playbook may not survive the
reboot.
To solve these problems, we have created a new base job for
OpenStack multinode jobs. (openstack-multinode-fips). We expect
to use this job as the base job for OpenStack multinode jobs
instead of the multinode job in zuul-jobs.
The openstack-multinode-fips inherits from openstack-fips, which
is a job defined in project-config that access the UA subscription
key and activates the UA subscription. This solves problem #1.
It then executes the enable-fips and multinode playbooks
(FIPS first!), which in turn, invoke the enable-fips and multinode
roles in zuul-jobs. This solves problem #2.
This has the unfortunate result of having to duplicate the logic
of the multinode/pre.yaml playbook in zuul-jobs here in
openstack-zuul-jobs instead, but I can't see a way around that.
Note that unless the variable enable_fips is defined to be true
in the job, all the FIPS logic is essentially a no-op.
If enable_fips is set to True, then jobs will also need to specify
nslookup_target for the post-reboot-tasks role invoked by the
enable_fips role.
Depends-On: I8a88d6a9bcf5725986b00b063e03686d3225b48e
Change-Id: I080df90af850088893976c8649aa528638c6f373
All the project that had periodic-stable-jobs template set in their
stable/queens branch have transitioned to End of Life, and their
branches were deleted [1]. This patch removes stable/queens from the
template as it is not needed anymore.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031323.html
Change-Id: Id587679ea84a4560a194b6af801f02c32a5b1295
tox4 need changes in tox.ini file to be compatible with it
and while fixes are merged in master and backported to stable
(if project decide to backport) let's cap the stable branch
testing to tox<4.
This only pin for jobs running for stable branches <=stable/zed.
Change-Id: Id468500746bc5c0986ec3334bfdafc24eeaba2f8
As per 2023.1 testing runtime[1], we need to move gate
test jobs on Ubuntu Jammy (22.04).
OpenStack tox base jobs are migrated to ubuntu jammy for
2023.1 onwards and they will continue running on Focal
until stable/zed.
[1] https://governance.openstack.org/tc/reference/runtimes/2023.1.html
Change-Id: If9bab60107ea2f049f0940766cf44ce3ebb002ee
TC is updating the 2023.1 cycle testing runtime to make the py38
as minimum python version to be tested (depends-on). This commit
updates the unit tests job template also on the same line.
Depends-On: https://review.opendev.org/c/openstack/governance/+/860599
Change-Id: Idea0b7b18f9fa7de7c07b4310667d61d90b95171
The build-openstack-puppet-tarball job consistently fails since
the default node set was switched from Focal to Jammy. This change
pins the node set back to Focal until we fix the current issue.
Change-Id: Ib1a55d624c72aa773ab03b736efed0699f35e946
The following py39 based jobs has been changed to py310 based in these
templates:
- periodic-jobs-with-neutron-lib-master
- periodic-jobs-with-oslo-master
- periodic-jobs-with-ovsdbapp-master
Change-Id: I96023fb323647465dacc450567d4a6adf6f59314
manchandavishal