854d9e270b
We have a couple validations that need to build an sdist now. But once it has been built in our temporary pristine clone, we don't need to build it again. Because we create a clean clone, we also don't need to worry about any stale dist builds. This adds a check to the sdist build logic to recognize if an sdist has already been built and skip it. There are also a few extra steps in the build process that are not needed for our purposes. The biggest is the new(ish) pbr behavior of building all release notes in the git tree if reno is present. This adds an environment variable flag to tell pbr not to do that. While we're at it, we don't need AUTHORS or CHANGELOG created either, so set the flags telling pbr to skip those as well. Change-Id: I15be9a12ff6684729980c40afae9625a8b8e550a Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
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.