summaryrefslogtreecommitdiffstats
path: root/docs/submodules
diff options
context:
space:
mode:
authorAric Gardner <agardner@linuxfoundation.org>2018-05-26 18:21:55 +0000
committerGerrit Code Review <gerrit@opnfv.org>2018-05-26 18:21:55 +0000
commit94bf5ed7a8b81342fdb341b06f1e5353f103256f (patch)
tree149d79ff6c920f3584b40f00129f65f5205bdd0f /docs/submodules
parent7fb50fc04e5f4211f7e4e5e84ec5298dc2c40b23 (diff)
Update git submodules
* Update docs/submodules/releng from branch 'master' - Merge "Verify and Create Tags from Release File" - Verify and Create Tags from Release File 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>
Diffstat (limited to 'docs/submodules')
m---------docs/submodules/releng0
1 files changed, 0 insertions, 0 deletions
diff --git a/docs/submodules/releng b/docs/submodules/releng
-Subproject a12bbcc26a75b51e185fd3e5b87c4834fbbffe0
+Subproject e9b2da6f4ea27f92e33516c49f79cfd8f8531da