Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Abandoned
-
None
-
None
-
None
Description
There are couple of things to be done to address build based on other branch instead of master
1. Change version in pom. xml
From 0.13.0-incubating-SNAPSHOT to 0.12.1-incubating-SNAPSHOT
2. Change release-build.sh
In function checkout_code()
Replace following line with
git checkout $GIT_REF (If branch will not be specified it will master otherwise it will be master, right? Do we need gitCommitHash for git checkout?)
Following
if [[ "$GIT_BRANCH" ]]; then
- Fetch any new branches (Not sure if this needed, won't hurt)
git fetch origin
- Get list of remote branches (Not sure if this needed, won't hurt)
git branch -v -a
- Get remote branch to work on
git checkout -b "$GIT_BRANCH Origin/$GIT_BRANCH
else
git checkout $GIT_REF
fi
3. Parse branch parameter
--gitBranch
GIT_BRANCH="${PARTS[1]}"
shift
;;
4. Commit above changes to branch-0.12 (later merge to master)
Once changes are checked-in extract code and run release publish with following command:
With DryRun
./release-build.sh --release-prepare --releaseVersion="0.12.0-incubating" --developmentVersion="0.12.1-incubating-SNAPSHOT" --releaseRc="rc2" --tag="v0.12.0-incubating-rc2" --gitBranch="branch-0.12" --dryRun
Without DryRun
./release-build.sh --release-prepare --releaseVersion="0.12.0-incubating" --developmentVersion="0.12.1-incubating-SNAPSHOT" --releaseRc="rc2" --tag="v0.12.0-incubating-rc2" --gitBranch="branch-0.12"
luciano resende Can you look at proposed change before I do changes and run build?
Attachments
Issue Links
- Is contained by
-
SYSTEMDS-1245 Improve release distribution consumability
- Closed