bcb61fece9
Git repo origins are now removed in CI jobs, so our detection of project short name from looking at the git remote now fails. This resulted in release announcements linking to "null" instead of the actual project location [0]. This updates the script logic to detect if that is the case and fall back to getting the repo name from the directory, which should be safe in a CI job since there is no manipulation of the clones repo directory name. Also cleans up an unused variable that was left from a previous refactoring. [0] http://lists.openstack.org/pipermail/release-announce/2019-December/008306.html Change-Id: I84e2cf258e9bc4541b7edde55a22a4be24bdb232 Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com> |
||
---|---|---|
data | ||
deliverables | ||
doc | ||
openstack_releases | ||
templates | ||
tools | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.zuul.yaml | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
LICENSE | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini | ||
watched_queries.yml | ||
yamllint.yml |
OpenStack Releases
This repository is used to drive release automation for OpenStack release deliverables, ultimately publishing them on the https://releases.openstack.org/ website.
Changes to this repository are proposed using Gerrit at https://review.opendev.org. This repository is managed by the OpenStack Release Management team.
For more information on how to use this repository, please read our reference documentation.
Who should use this repository
All official OpenStack software should go through the OpenStack Release Management team team to produce releases. Exceptions to this rule are granted by the Technical Committee and documented in the openstack/governance repository ('release-management' key in reference/projects.yaml).
Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.
More information
You can reach the Release Management team on the #openstack-release channel on Freenode IRC, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.