openstack/project-config
Code Issues Proposed changes
3d72773921
project-config/roles/copy-release-tools-scripts/files/release-tools
History
Előd Illés bb686e8deb [release-tool] Workaround for getting dist_name 
'python3 setup.py --name' with the recent pbr started to print
'[pbr] Generating ChangeLog [..]' to stdout, which causes to gather
wrong 'dist_name'. The workaround is to add 'tail -1'.
This should be removed when there is a better way to get dist_name.

Change-Id: Ia519eb8aec4292ab79f285f4cb828b6fbb4421d5
2024-08-22 11:28:02 +02:00
..
add_release_note_page.sh Use python3 to run release note script 2021-01-04 12:14:36 +01:00
change_reno_branch_to_unmaintained.sh Update reno update to check whether series exists 2024-02-06 09:23:08 +01:00
clone_repo.sh Use updated git cache dir default path 2024-02-01 21:11:42 +01:00
eol_branch.sh Update jobs for OpenDev 2019-04-20 13:51:05 +00:00
functions Retire django-openstack-auth 2021-07-16 22:10:16 +05:30
launchpad_add_comment_set_status.py Set launchpad bug Fix Released after adding comment 2021-09-02 22:45:31 +00:00
make_branch.sh [release-tool] Fix branch creation exceptions 2024-03-14 14:56:37 +01:00
process_release_requests.py Use yaml.safe_load in release jobs 2024-08-21 12:23:31 -07: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 Add the branch to the release metadata 2023-06-15 13:22:54 -07: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 [release-tool] Workaround for getting dist_name 2024-08-22 11:28:02 +02: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