summaryrefslogtreecommitdiffstats
path: root/jjb/releng/releng-release-tagging.sh
AgeCommit message (Collapse)AuthorFilesLines
2018-05-26Revert "Remove noop for tag creation."Aric Gardner1-1/+1
This reverts commit dc4b9d1ad316e9055ccb3767c4572ad22cbe43a5. Change-Id: I3bec4ef84dcb7e56d80b4df78b487f7caa931f3e
2018-05-26Remove noop for tag creation.Aric Gardner1-1/+1
This script is tested, and should now be allowed to create tags. Change-Id: Ia87341c9cb6397700442a11c38d502fed8dd4743 Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
2018-05-25Verify and Create Tags from Release FileTrevor Bramwell1-0/+70
Updates the releases verify and merge jobs to check release files for the following: - commits exist - commits are on stable-branch If both of these criteria are met and the patch is merged, the repos will be tagged at the specified commits and pushed. If a repo has already been tagged but not on stable-branch the job will not exit, but will warn that the commit doesn't exist on the correct branch. This is because tags should never be removed. This adds an additional script 'repos.py' that provides an quick interface for pulling out information from release files, along with the script 'release-status.sh' for checking the status of tags. NOTE: The branch creation script has been disabled until it can be reworked. Change-Id: I498bc74f20aa50d2bd321771f20a77905b246399 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>