openstack/project-config
Code Issues Proposed changes
a3f4b2ac4d
project-config/roles/copy-release-tools-scripts/files/release-tools
History
Sean McGinnis 323eb4d68c
Tighten formatting for new branch reno page title 
Some have pointed out that the generated page title is not strictly
correct for a valid RST title. This adds some additional formatting of
the text to make sure it is completely valid.

Change-Id: I8652be3dc987629a8acca7a1584086fc4e2f4636
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2019-09-12 10:40:19 -05:00
..
add_release_note_page.sh Tighten formatting for new branch reno page title 2019-09-12 10:40:19 -05:00
clone_repo.sh Update jobs for OpenDev 2019-04-20 13:51:05 +00:00
eol_branch.sh Update jobs for OpenDev 2019-04-20 13:51:05 +00:00
functions Handle TOX_CONSTRAINTS_FILE as well as UPPER_CONSTRAINTS_FILE 2019-05-20 20:16:56 +02:00
launchpad_add_comment.py Move release-tools out of jenkins/scripts 2018-02-27 19:27:35 +01:00
make_branch.sh update the branching script to include a semver bump 2018-10-12 11:49:46 -04:00
process_release_requests.py Merge "ignore the series_status.yaml when processing release requests" 2018-04-27 09:41:46 +00:00
process_release_requests.sh Move release-tools out of jenkins/scripts 2018-02-27 19:27:35 +01:00
py3-requirements.txt Move release-tools out of jenkins/scripts 2018-02-27 19:27:35 +01:00
README.rst Move release-tools out of jenkins/scripts 2018-02-27 19:27:35 +01:00
release.sh use python3 to run launchpad commenting script 2018-06-21 16:30:26 -04:00
requirements.txt Move release-tools out of jenkins/scripts 2018-02-27 19:27:35 +01:00
update_constraints_for_branch.sh Move release-tools out of jenkins/scripts 2018-02-27 19:27:35 +01:00
update_constraints.sh Move release-tools out of jenkins/scripts 2018-02-27 19:27:35 +01:00

README.rst

Release Tools

release_from_yaml.sh

This script takes YAML files describing deliverables to release (like those living in openstack/releases) and calls the release.sh script (see below) to apply the corresponding tags. It will create a tag for the last release mentioned in the file(s). You can point it to specific YAML files, or to a local git repository (in which case it will look at the files modified in the most recent commit).

Examples:

./release_from_yaml.sh ../openstack-releases deliverables/mitaka/nova.yaml

Call release.sh for all repositories mentioned in the last release added to ../openstack-releases/deliverables/mitaka/nova.yaml

./release_from_yaml.sh ../openstack-releases

Look into the git repository at ../openstack-releases for deliverable YAML files modified at the last commit, and call release.sh for all repositories mentioned on the last release in each such file.

release.sh

This script creates a tag on a given repository SHA and pushes it to Gerrit. Additionally it will add a message on Launchpad bugs that are mentioned as "closed" in git commit messages since the last tag on the same series.

Example:

./release.sh openstack/oslo.rootwrap mitaka 3.0.3 gerrit/master

Apply a 3.0.3 tag (associated to the mitaka series) to the gerrit master HEAD of the openstack/oslo.rootwrap reporitory, and add a comment for each closed bug mentioned in commit messages since the previous mitaka tag (3.0.2).

branch_from_yaml.sh

This script looks at the deliverable files to decide how to create stable branches.

$ branch_from_yaml.sh ~/repos/openstack/releases mitaka
$ branch_from_yaml.sh ~/repos/openstack/releases mitaka
$ branch_from_yaml.sh ~/repos/openstack/releases mitaka deliverables/_independent/openstack-ansible.yaml