We've created integrated linters check job a while back and it's successfully
working for several releases. At the moment we experience difficulties
with future maintenance of the linters check from the openstack-ansible-tests
repo. So instead of fixing current one, we replace it with modern version of
the test.
Change-Id: Iebcc755c22b8b34e06be95acd48c3ab9cecf953b
Since we copy all release notes to the integrated repo there is not need
in publishing release notes for each repository. We should only verify their
validity and linting.
Change-Id: Icd059fb0ec832e8b7b4e6f9a671b11959b6bda26
Currently this role doesn't test the integrated jobs.
With the dynamic execution of the roles, this role
also get tested by the integrated repo.
Change-Id: I615beebe4f323e64a963ecc534b1b0c20fd58141
This patch adds the Debian jobs for this role to make sure
it's always passing as well as updates the meta to reflect
it's support of Debian accordingly.
Depends-On: I9a92b73c419a0dc1cca40dacfef75de61a61db94
Change-Id: I6c3b50b6154bb6893fbaf5b1f05da08b199184b3
The swift3 middleware has been deprecated in replacement with the
s3api middleware instead. This removes all the swift3 references
to hopefully enable someone to cleanly add s3api eventually.
Change-Id: I3a8a1ab861ec81b1f4f8dbc02a6a332d4ce495b8
In order to do a more complete verification of any patches,
we add a full uncontainerised OpenStack deployment to do the
functional testing using the integrated repo. This replaces
the previous functional test mechanism.
Any additional role tests are left as-is. They will require
some extra implementation in the integrated build before they
can be transferred.
The CentOS distro. installation was missing RPMs which meant
some binaries was missing, this patch adds those as well.
Depends-On: https://review.openstack.org/648502
Depends-On: https://review.openstack.org/648551
Depends-On: https://review.openstack.org/648575
Change-Id: I4b73967aacb92b63f9f01514979e31aa2fb5f61e
Add Leap 15 distro_install job and replace Xenial with Bionic since the
former does not provide packages for recent OpenStack releases.
Change-Id: I946b225cc43f9195f63b064a33392476270f7d32
Now that we're using the general templates, we can slim down
the role test definitions. We can also remove tests which are
not being watched, or which are fundamentally broken. With
this we can also remove unused scripts/plays.
We do the following:
1. We remove the 'upgrade' job, given that it's been broken
all cycle due to the way the job executes and we need to
regroup to figure out another way to do it. The associated
scripts are also removed.
2. We remove the 'pypy' tox target. The job was removed some
time ago, but the tox target left behind. The associated
inventory is also removed.
3. We remove the 'multireg' jobs. The jobs have been failing
for some time and are very complex. If multi-region tests
are re-implemented, they should be done in a simpler way -
probably best using multiple nodes, rather than trying to
fudge it on a single host with containers. The associated
scripts and inventory items are also removed.
4. We rename the 'func_swift3' tox target to 'swift3', and
reconfigure the job appropriately. The verbose logging for
ansible is also removed, given that we have ARA to provide
decent diagnostic output.
Change-Id: I411fcaac9a1ddf17996d771f13b2de7e775e4a60
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: Ic2c970f3bc7baff38f72e4deaf9fc9c87271be71
Story: #2002586
Task: #24319
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: If3249c7e89ca3a0f65fc340e84d4e2e2c82d16db
Story: #2002586
Task: #24319
In order to have more centralized configuration, switch the role
to use the project-template instead.
Change-Id: I5d3a265ee6fd71c9f47dcd6226b1698eae3c470a
The rabbitmq/oslomsg groups are now required by the
keystone role, so we add them to the inventory and
ensure that the test playbook install the services.
Also, the multi-region tests are set to non-voting
to unblock the swift repo for other patches to
resolve the issue.
Change-Id: I4e2bbdff7a89b204723e7937667854c412051347
The pypy job never worked and nobody contributed on making
it better.
We should remove it until people are explicitly wanting to
improve the situation.
Change-Id: I680b2c07f867db828774e906b6743e3957a40364
The extra jobs that we have are not something that is needed, we simply can
set the jobs to non-voting in the project definition and avoid having non
voting jobs.
Change-Id: Ie029533bca3a742c20c7e333f97f9217c4be2340
Distributions provide packages for the OpenStack services so we add
support for using these instead of the pip ones. However, functional
testing is not complete yet since it requires tempest to be in the swift
virtual environment which doesn't exist for distro installs. As such,
for functional testing to cover this method of installation it needs
to be changed quite a bit.
Change-Id: Id75e56440685df407a9991018dc07b5a75429082
Implements: blueprint openstack-distribution-packages
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Ifff40bdf0aaf9020d3b3e44cfb15055f2824266e
Until the bug #1729263 is resolved, we should move back to
non-voting centos, to avoid an useless series of rechecks.
Change-Id: I930a0458c10625e2f795f4fba76675f5b93a6f7d
Initially the intent for adding this was to better test
any patches for roles together before they merge, but it
has had the unintended side-effect of causing patches to
take much longer to merge (because they all get lined up
in a single queue, rather than independent queues) and
a lot more infra resources are used (because a patch
that fails at the top of the queue will result in all
subsequent patches restarting all their tests).
As discussed in the channel, we'd prefer to revert back
to the previous independent queue method of testing. It
has served us well.
Change-Id: I717e111e8cc85f8396bddf317a2a27969a5728e7
Currently the linters test is in the project-config
repository, but those are meant to be used for standard
jobs which do not require any repository other than the
one given. Our lint tests use the 'openstack-ansible-tests'
repository, so we should rather use our own job definition.
Change-Id: Ie7416e87851463e94bc11147faa277b5bf60e106
Depends-On: I0391ec310c4eede436011a48490e3c524c8ddf4d
This changes the a-r-r with the proper version, and fixes
the repo path for role upgrades:
The role will, during test-upgrade-pre, have its current branch
checked out, and will deploy the current branch infrastructure,
including the generation of the constraints.
Then, the installation of previous branch of the role will use
the constraints for its previous version, but will have no
constraints for it, and fail.
We need to generate the constraints for the previous version too.
This should do it.
This patch also implements an initial set of jobs intended to
match the current job execution method. It does not intend to
improve how the jobs are executed - only to replicate what is
currently in openstack-infra/openstack-zuul-jobs and provide
the platform to iterate on.
Change-Id: I4aa7591c931501490e706b9d61ba0bc12c006baa
Dmitriy Rabotyagov