Tripleo-ci jobs are broken after latest release of setuptools 61.0
because of breaking changes which are not backwork compatible,
details in related bug and [1].
Users that don't set ``packages``, ``py_modules``, or ``configuration`` are
still likely to observe the auto-discovery behavior, which may halt the
build if the project contains multiple directories and/or multiple Python
files directly under the project root.
To disable auto discovery, one can do below in setup.py
~~~
setuptools.setup(..,packages=[],..)
~~~
or
~~~
setuptools.setup(..,py_modules=[],..)
~~~
Also, adding ^setup.*$ under irrelevant-files as content-provider
parent[2] also have same.
Reviewed: https:/ /review. opendev. org/c/openstack /tripleo- upgrade/ +/835790 /opendev. org/openstack/ tripleo- upgrade/ commit/ 4ca0d9a31c4290b befff6b3529d43a 6abdaaa399
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/ussuri
commit 4ca0d9a31c4290b befff6b3529d43a 6abdaaa399
Author: Brendan Shephard <email address hidden>
Date: Mon Mar 28 15:18:18 2022 +1000
Disable auto discovery
Tripleo-ci jobs are broken after latest release of setuptools 61.0
because of breaking changes which are not backwork compatible,
details in related bug and [1].
Users that don't set ``packages``, ``py_modules``, or ``configuration`` are
still likely to observe the auto-discovery behavior, which may halt the
build if the project contains multiple directories and/or multiple Python
files directly under the project root.
To disable auto discovery, one can do below in setup.py
~~~ setup(. .,packages= [],..)
setuptools.
~~~
or
~~~ setup(. .,py_modules= [],..)
setuptools.
~~~
Also, adding ^setup.*$ under irrelevant-files as content-provider
parent[2] also have same.
[1] https:/ /github. com/pypa/ setuptools/ issues/ 3197 /opendev. org/openstack/ tripleo- ci/src/ branch/ master/ zuul.d/ base-upstream. yaml#L92
[2] https:/
Related-Bug: #1966382 3bd81699e505588 133cfe02f52 b4354370f36b916 caf7e21c2a)
Change-Id: I643952b64d557f
(cherry picked from commit 13d7a4c60ed6d40