summaryrefslogtreecommitdiffstats
path: root/jjb/releng/releng-release-tagging.sh
AgeCommit message (Collapse)AuthorFilesLines
2018-11-23Rework creating tags & branches from release filesAric Gardner1-4/+0
Old method could not properly handle both branching and tagging on changes to the release file. Proposed method: jjb calls: jjb/releng/branch-or-tag.sh for both verify and merge jobs. branch-or-tag determins nature of the change to "releases/branch/project.yaml" and calls releng-release-tagging.sh or releng-release-create-branch.sh The scripts above handle both verify and merge operations based on if [[ $TAG_EXISTS = false && "$JOB_NAME" =~ "merge" ]]; and if [[ $REF_EXISTS = true && "$JOB_NAME" =~ "merge" ]]; then both scripts check that the ref exits in verfiy and merge stages. if releng-release-create-branch.sh creates a branch it then also calls releases/scripts/create_jobs.py Change-Id: Ieb99de5e4df100af59ecc818f52b0831383b2b62 Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
2018-06-29Fix release tagging scriptTrevor Bramwell1-1/+1
git cat-file can't output the tag information for a tag, but it can output the commit information a tag points to. Change-Id: I147941e2c0ba6defe212dbd0fc8c8a3a1fe0c728 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-06-20Fix release tagging noopTrevor Bramwell1-1/+1
When the release job runs to tag the repos it should push the tags back to Gerrit. This was originally a 'noop' for testing. Change-Id: Ifbecbccda1ae123c7b8f0d59eefa727784d10acd Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
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>