5 The release merge job is a one way operation.
6 Given this, Release jobs should only exist in the format
7 {project-name}-release-verify and
8 {project-name}-release-merge
9 As these jobs trigger from a change to any branch/**
10 These jobs Must Exit 0 if release job has already tagged a repo.
11 Inevitably a release file will be pulled in from master to branch
12 or a remerge will be requested This will again trigger the release jobs.
13 since in this case the repo is already tagged, the job should not report
14 a failure. This is solved by having the verfiy and merge exit 0 when the
15 repo is already tagged
17 Rather than use project as defined in the release file use
19 This changes PROJECT="optf/osdf/foo/bar" to
20 optf-osdf-foo-bar so that we can fetch the log files.
21 by changing /'s in the project names to -'s