Ussuri Communtiy-wide goal:
https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
Remove explicit listed jobs from check queue, they are in the templates.
- Update jobs
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Remove obsolete sections from setup.cfg:
* Wheel is not needed for python 3 only repo
* Some other sections are obsolete
- Update classifiers
- Update requirements, no need for python_version anymore
Co-Authored-By: Andreas Jaeger <aj@suse.com>
Change-Id: I4a1976c78b0fe69cc1b423c516d557838cb6d59b
Paunch is now disabled by default except on a few jobs when Pacemaker is
still running with Docker; which is the case of scenario004.
Let's remove the jobs where Paunch isn't exercised, to save resources.
And also add the 'irrelevant-files' parameter to skip the job when not
needed.
Note: it's not defined in that file but the OVB jobs running on CentOS7
also need to be executed until they are moved to CentOS8; since
Pacemaker and Docker are used; therefore Paunch is used to manage the
non-HA containers.
Change-Id: Ie8d2515b46f70b5ca39625bd0272d933f3b0ffec
..for Greater Good.
Save CI resources and shorten wait-in-zuul-queue times
for other patches, when tox/pep8 checks failed.
NOTE: for example, standalone jobs are defined as a template in
tripleo-ci, and here we are adding and override the listed jobs for the
dependencies/files options. If a job is added to the standlone template
in tripleo-ci, we need to add the job and dependency here manually.
If we won't, that job will be consumed as is and run w/o dependencies.
That is the price to pay for not having overrides managed centrally in
tripleo-ci. The latter wouldn't work neither as a single template
cannot fit all the specific needs of numerous tripleo repos. So the
final call was made to manage overrides via local overrides for tripleo
repos.
For core openstack python projects it might make sense to
not split them apart and run them all together. For things like
TripleO/Kolla/Puppet/etc where we have layers of interactions that can
be affected by the results from the linters/unit jobs it makes
sense to split them out.
For example, in tripleo since we use packages, if the unit test fails
the integration test may fail because when we go to built the package
with the new source, the unit test int he package build fails. Thus
we know that'll be a wasted execution and you won't actually get any
results.
An alternative Today:
patchset one:
pep8 SUCCESS
unittest FAILURE
integration FAILURE
patchset two:
pep8 SUCCESS
unittest SUCCESS
integration FAILURE
patchset three:
pep8 SUCCESS
unittest SUCCESS
integration SUCCESS
Future:
patchset one:
pep8 SUCCESS
unittest FAILURE
integration SKIPPED
patchset two:
pep8 SUCCESS
unittest SUCCESS
integration FAILURE
patchset three:
pep8 SUCCESS
unittest SUCCESS
integration SUCCESS
This may not be true for devstack but if the unit
tests are failing, then the code is likely bad (backwards
compatibility/wrong assumptions about change/etc) and we shouldn't be
running an actual deployment.
Related upstream ML threads:
* http://lists.openstack.org/pipermail/openstack-dev/2018-March/
127869.html
* http://lists.openstack.org/pipermail/openstack-discuss/
2019-February/003142.html
Change-Id: I967ff0323756e63e9bd66049080dde2a870399fd
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.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: Ieceb6eb299abfb640ce9cb78e26302469b7554b5
Story: #2002586
Task: #24341
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: I462d3aad64a3ff339e0fd84126afd8e431afb18f
Story: #2002586
Task: #24341
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Id655209306fa0cda1d012dac6996dbfc95dbbc00
- Pike: run ovb-containers
- Queens and beyond: run ovb-ha (containerized)
Depends-On: I2ce9376def4d2c7637573420760a79a0ae3af4b2
Change-Id: I7aad503175d16482e44e8ca86375eed6c82a6691
Emilien Macchi