...
A set of scripts have been developed to make the release process somewhat less tedious. The scripts are located in the policy/parent repo here.
Script | Description |
---|
bumpSnapshots.sh | bumpSnapshots.sh - generate commits to bump the snapshot version and update references to snapshot references on any repos that need to be bumped or updated
usage: bumpSnapshots.sh [-options]
options -h - this help message -d data_file - the policy release data file to use, defaults to './pf_release_data.csv' -l location - the location of the policy framework repos on the file system, defaults to './' -i issue-id - issue ID in the format POLICY-nnnn
examples: bumpSnapshots.sh -l /home/user/onap -d /home/user/data/pf_release_data.csv -i POLICY-1234 bump snapshots on the repos at location '/home/user/onap' using the release data in the file '/home/user/data/pf_release_data.csv' |
generateCommit.sh | generateCommit.sh - generates a new commit or a patch on an existing commit for PF releases
usage: generateCommit.sh [-options]
options -h - this help message -l location - the location of the policy framework repos on the file system, defaults to './' -r repo - the policy repo to which to commit -i issue-id - issue ID in the format POLICY-nnnn -e commit-header - the header for the commit -m commit-message - the message body for the commit
example: generateCommit.sh -l /home/git/onap -r policy/pap -i POLICY-1234 -e commit-header -m commit-message create a new commit or update an existing commit on policy/pap with the given details |
getReleaseData.sh | getReleaseData.sh - gets information from the checked out Policy Framework repos for the release process
usage: getReleaseData.sh [-options]
options -h - this help message -b branch - the branch to release on, defaults to 'master' -d data_file - the policy release data file to create, defaults to './pf_release_data.csv' -l location - the location of the policy framework repos on the file system, defaults to './' |
mkart.sh | mkart.sh - create the release yaml file to release the current snapshot on the current repo
usage: mkart.sh [-options]
options -d - create a release yaml foie for a repo that has Docker images |
mkdock.sh | mkdick.sh - create the release container yaml file to release the docker images on the current repo
usage: mkdock.sh [-options]
options
-d - create a release yaml foie for a repo that has Docker images |
newReleaseSnapshots.sh |
|
releasePhase.sh |
|
releaseRepo.sh |
|
releaseRepoImages.sh |
|
updateOomImages.sh |
|
updateParentRef.sh |
|
updateRefs.sh |
|
The scripts:
- Operate on a cloned copy of all 13 Policy Framework repositories
- Break the release process into a set of phases, which are executed one after another to perform a release
- Can release on the Master branch or any other branch
- Act on the POM files, Docker files, the maven and docker release files, the version.properties files, and the pf_release_data.csv file in the repos, updating the references in those files as required for each phase
...