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=[],..)
~~~
[1] https://github.com/pypa/setuptools/issues/3197
Releated-Bug: #1966382
Change-Id: I8db5e382576a820f756cc936ca0fe7ca6d0ec1d1
This is not an actual python project, so there is an amount of cruft
in the repo that is not needed. However, it does generate tarballs in
OpenStack Infra, so it needs the tox venv environment and the pbr
setup.py stuff. It also is totally possible to check python files in
the repo for flake8 violations, so set that up.
Change-Id: Ifb94f65912716efe1c4596d552beee92d2dc3d6a
Uses pbr-0.5.20 glob support to install elements.
This packaging will facilitate tripleo-image-elements being
consumed by CI tooling, enabling tests which require customized
images.
Change-Id: Id0ce2f9954f487ef2375e51cc8287999b82396f2
Per http://wiki.openstack.org/ProjectTestingInterface we enable all
of the commands except build_sphinx because we do not have any sphinx
documentation as of yet. Includes babel support though there are no
properly internationalized strings just yet.
Change-Id: Iae6e6b3f9e605106f4575196fa5527d2187255df
Ghanshyam Mann