Fedora-Cloud-Base-29-1.2.x86_64 is removed from openstack local mirror.
Update to use Fedora-Cloud-Base-30-1.2.x86_64 for test jobs.
Change-Id: Id3026a115e3a044b3dc00030fd6d82549dc189b6
Something are introduced in this patch:
* As devstack-gate/devstack-vm-gate-wrap.sh is not really zuul v3
native, we move all configs in to `devstack/lib/heat` and .zuul.yaml.
* Remove extra configs process in devstack. Like setup tempest(which
is well covered by tempest itself.) or overlapping heat test configs setup.
Use tempest config for all heat_integration tests. Also remove
heat_integrationtests/common/configs since they're no longer required.
* copy post.yaml for grenade jobs. As we migrate to zuul v3 for
functional tests but not grenade (not yet), the post.yaml should exists
under grenade dir. since it's only required by grenade jobs.
* Use post.yaml in functional tests for cleanup test environments.
Story: #2007056
Task: #37908
Depends-On: https://review.opendev.org/701105
Change-Id: I4f531161a7222e2c2a21f8d483f9c2a1d91dc38d
Periodic stable jobs don't run on stein, only up till rocky as
periodic-stable-jobs template is missing from master and stein
branches.
Change-Id: Ic7fa6a2bef3db1f6f2548d1c792e0cef29787586
This goal is to implement the process set out in the 2018-10-24 Python
Update Process TC resolution[1], for the Train cycle to ensure unit
testing is in place for all of the Tested Runtimes for Train[2].
In practice, this generally means adding unit tests for Python 3.7 and dropping
unit tests for Python 3.5. Using the Zuul template for Train will ensure that
all projects that support Python3 will be tested against the agreed runtime
versions, and make it easier to update them in future.
[1]https://governance.openstack.org/tc/resolutions/20181024-python-update-process.html
[2]https://governance.openstack.org/tc/reference/runtimes/train.html
Change-Id: I62abb218bb314345dd7da1cbf9133d10db9696ff
Depends-On: https://review.opendev.org/#/c/641878/
Switch all Ubuntu Xenial integration test jobs to Bionic (by depending
on the patch that changes them globally.
Change-Id: I5b6c870a12892950c3e8d3aeadffe23ffbf8219e
Depends-On: https://review.openstack.org/639096
Non-containerized multinode scenario jobs are no longer supported
and should be removed from zuul config.
Change-Id: I0c98aecd82478fbf7e2b2a45d5b2664290155ed9
Update the jobs that were explicitly using python 3.5 and have them
just use python 3 without specifying a minor version.
Change-Id: I38734f2956a30c01ff51e2d74a9c248e4304d08b
This reverts commit 4e8a3ca6b2041c170f4073499ee0315616396af2.
This is handled generically with this change and its dependency:
https://review.openstack.org/#/c/606853/
Change-Id: Ic79cc07a2d11772c1892b2db8c4c02cc7be4081c
In order to get openstack/placement installed as part of the
heat grenade jobs, we have to list it as a required project.
Needed by https://review.openstack.org/604454/
Change-Id: I58fae5f56fdbcb4fc084689bde95f1a2c4bfad0f
Continue to test Heat's interaction with the Octavia API without relying on
Octavia's interaction with Nova, Neutron &c. which is known to be unstable.
Change-Id: I8765aceee09ada3086abc704b7f73ce240e21847
Use openstack-tox-cover template, this runs the cover job
in the check queue only.
Remove jobs and use template instead.
Change-Id: I251086151a23c78f99f39d55b4db36d1db5bc9a0
* Remove "queue: heat" from check queue, this is not needed.
* Use openstack-lower-constraints-jobs template.
Change-Id: Idde37f299c1cde86b2169fd174539249c23c9962
Some of the project templates brought in via
https://review.openstack.org/#/c/576193/ should have been left in the
project-config repo because they only run on the master branch. This
patch removes those templates.
Change-Id: I727a9ac03781f86845d1af0b2a2ae672665b30db
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs as part of the
python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I33e99114889052d6e610a305c5fb659822d5b0d4
Story: #2002586
Task: #24298
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: I4c5227d740cdb0bc9e08ccdce27b0ca73fb4ded3
Story: #2002586
Task: #24298
I jumped the gun a bit here, and it turns out that all branch-specific
jobs will be maintained in openstack-infra/project-config, and not moved
to project repos.
Change-Id: Ia54bd7d29717e2fb025c9547b852c4ec00cbcbd2
All projects are moving their Zuul configs from the
openstack-infra/project-config repo to their local repos. Once this change
has been backported to all open stable branches, we can remove the
centralised config.
translation-jobs-queens is omitted because we will set that up on the
stable/queens branch specifically (in place of translation-jobs, which runs
only on master).
Change-Id: Ia182e4dcf1a0b8e3af124b6676b20e6adb55f76b
neutron-lbaas has been deprecated since long. Let's remove the
service from gate jobs and skip the relevant tests.
Change-Id: I8eede46ed2ad014522e00d28b0b7c0b194a0b996
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: I72fd5f8c87133713cd272de210b7e957880f48f9
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I43b8a36e6ba8457c9594dc4ad579167f95d91d39
These were disabled in I55e204b72cd5a2876576852b10ad09f24d04beb4 to
reduce the gate failure rate while we eliminated duplicate tests in heat
and heat-tempest-plugin.
Change-Id: Ifd2aececfa5b1b0f2c8959ad500d4d3197427d19
This patch propose to use heat tempest plugin for potential
co-gating integration tests.
These tests are consider as potential co-gating. And we now
already maintain them in heat tempest plugin.
This also disables all except two of the gate/test jobs, to enable us to
land this series and stop the carnage. The jobs will be re-enabled once
all of the duplicated tests have been eliminated.
Change-Id: I55e204b72cd5a2876576852b10ad09f24d04beb4
Run tripleo-ci jobs with scenario002 on experimental pipeline
of Heat (with "check experimental").
Services that are deployed in scenario002 are in
tripleo-heat-templates repo:
ci/environments/scenario002-multinode-containers.yaml
Change-Id: Ifd6507694d98a7dfc03bb342d60aa2bbf0eac778
Now mitaka and newton already mark as EOL, so we should remove any
branch limit that relative to those branches.
Also since we have dependent zuul jobs for each branch, we remove
ocata branch limit from master.
Change-Id: Ide2ddbe4d50faa0356992b55d99c1b1af8a44a35
Note: We still have to change grenade jobs to use
the plugin, before removing the plugin from tree.
Change-Id: Ie63f25e724ed3fbd42adcf5bb2d625c2fec67df1
Zuul now supports including the file extension on the playbook path
and omitting the extension is now deprecrated. Add `.yaml` back for
playbook path.
Change-Id: I4a2ae5f28740e41f5b77c05954e7ea4562016be9
