Rework creating tags & branches from release files 59/62659/10
authorAric Gardner <agardner@linuxfoundation.org>
Thu, 20 Sep 2018 17:50:02 +0000 (13:50 -0400)
committerAric Gardner <agardner@linuxfoundation.org>
Fri, 23 Nov 2018 20:21:24 +0000 (15:21 -0500)
commit52d29ad095ad729a0287ec07a2c19072b4fb672b
tree912efab92e18a2fe3b0cd874c9a4b5adeda7b681
parent1569d338abfadc2a851e7f842c3fcc22e2d7998d
Rework creating tags & branches from release files

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>
jjb/releng/branch-or-tag.sh [new file with mode: 0755]
jjb/releng/releng-release-create-branch.sh
jjb/releng/releng-release-jobs.yaml
jjb/releng/releng-release-tagging.sh