openstack
/
project-config
Code Issues Proposed changes
project-config/roles/copy-release-tools-scripts/files/release-tools
History
Sean McGinnis 6afe343380
Include octavia files when updating branch constraints 
Patch I8eba64c886c187c8652f94735ca6153702203d17 added logic to update
the constraints URL for a project specific file, but adding the file
before committing and submitting the changes was missed, resulting in
git review erroring during the rebase step of submitting the review due
to unstaged files.

Change-Id: I4d87546f12c4a866e9c666e83c42ad8d07a637a3
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
 		2020-04-23 15:37:42 -05:00
..
README.rst Move release-tools out of jenkins/scripts 2018-02-27 19:27:35 +01:00
add_master_python3_jobs.sh Make job template update best effort 2020-04-11 14:45:20 -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 Include octavia files when updating branch constraints 2020-04-23 15:37:42 -05:00
launchpad_add_comment.py Update hacking, fix errors/warnings 2020-01-14 09:40:45 +11:00
make_branch.sh Add tooling to update python jobs on branch creation 2020-04-08 08:44:14 -05:00
process_release_requests.py Fix branch to series matching logic in job updates 2020-04-08 15:40:05 -05: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
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.sh Update update_constraints for Py3.8 2020-04-15 14:55:38 +02:00
update_constraints_for_branch.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