We don't want to use Extended Maintenance (EM) tags, since these are
just markers of a point in time and not available as released artifacts.
Change-Id: If552f7ffc22d4b25769c14c083179eecf5a93158
The current code worked only if the project was using the project_name
in kolla/common/config.py, rather than the tarball_base name. This is
only true on master - on stable branches we may switch to use the
tarball_base name, so the regex won't match.
Change-Id: I839649e6ef662ae3ff320edb3106da818956d26d
We use the stable branch of the requirements project.
Also add an exception for the crane project, which is not managed by
OpenStack releases.
Make use of 'tarball_base' field to handle tarball renames.
Change-Id: I05186d9a3e21615e6b49c62cea83bc4bde4702fe
monasca-thresh package is not published in
tarballs.openstack.org and fails to detect
proper version for it.
Add to external managed packages list
Change-Id: I5da4da1f5291e993fdcd04177c634147204ad9ed
Gnocchi is moved out of openstack/releases project.
Version-check need to be updated with gnocchi in
skipped projects.
Closes-Bug: #1703386
Change-Id: I2b37aeb7042756be534559615878e698275783c6
Bandit was not running in all directories
due missing -r parameter.
Also, this change fix bandit errors.
* Add nosec to subprocess module
* Change /tmp/releases to .releases
* Change /tmp/ to tmp/, tmp/ is not checked
and in unittest is not an issue, simpler that mocking tempfile
and make more complex tests.
Change-Id: I42bafa4707a9a4d1faeb01cb9b5a843f56280deb
In old implementation, version-check always get the latest versions
rather than versions for certain release. it is useless for stable
branch. And it parses from tarballs.openstack.org site, which is
very slow.
In this new implementation, version-check gets versions from
openstack/releases repo, which is faster and accurate. It also support
get versions for certain OpenStack release. For example, get the Ocata
latest release version.
./verion-check.py --openstack-release ocata
Closes-Bug: #1554337
Change-Id: Ie8951625817d82f38cf820cf9bd44ae447e2eb75
Consistently set the search path to prefer PROJECT_ROOT as the source
of packages to import if we are using local tools instead of pip
installed kolla tools.
TrivialFix
Change-Id: Idd1d98bb82a8f1ddb32d1bdb23f346b461534b9f
In some part in the code we import objects. In the Openstack style
guidelines they recommend to import only modules.
http://docs.openstack.org/developer/hacking/#imports
Change-Id: I4b55cae8c2672f82025a95112b14d441d66f9d6d
Radosław Piliszek