diff options
| author |   Aric Gardner <agardner@linuxfoundation.org> | 2018-05-26 18:21:55 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@opnfv.org> | 2018-05-26 18:21:55 +0000 |
| commit | 2b921e47f09880244155bb5de20ffe9b312c44de (patch) | |
| tree | 1aee090bcda2b59d28a42dd598fd28575002f91c /docs/glossary | |
| parent | 3b2e004f9c01cb7d7efd270863355073b0a0728a (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/glossary')
0 files changed, 0 insertions, 0 deletions