828e285701
We use release-types as a way to verify that versions are compatible and if needed reflected accurately in the code (puppet, xstatic). If one isn't set explicitly then we assume python-service. In certain circumstances (anything other than the first release in a series) we also perform python specific requirements checking on all 'python' types. Add a new 'generic' type that uses the same rules to validate version numbers but wont run any python specific checks. We need this a projects (like monasca-thresh) will fail the requirements check for 2nd or greater releases[1]. An alternate would be to have the requirements code check if setup.py exists before calling it but that seems like the wrong layer to me. [1] http://logs.openstack.org/54/652854/1/check/openstack-tox-validate/80df01c/job-output.txt.gz#_2019-04-16_06_08_00_636538 Change-Id: I3fcde5eb266f954fddb6871ce8690b93b8fd7a8d |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| CrossProjectLiaisons.txt | ||
| fixtures.py | ||
| test_deliverable.py | ||
| test_new_release.py | ||
| test_npmutils.py | ||
| test_project_config.py | ||
| test_puppetutils.py | ||
| test_redirections.py | ||
| test_requirements.py | ||
| test_series_status.py | ||
| test_validate.py | ||
| test_versionutils.py | ||
| test_wiki.py | ||