-
Notifications
You must be signed in to change notification settings - Fork 49
Releasing a new version
micro-infra-spring is released automatically using micro-common-release mechanism. To trigger a new release process it is enough to put somewhere into a commit message a magic command [#DO_RELEASE]. It doesn't have to be in the first line, e.g.
git commit -m "Trigger release" -m "[#DO_RELEASE]" --allow-empty
More details are available in micro-common-release wiki.
Legacy warning. The legacy version is deprecated and a manual release process was left to discourage people from the development work done in that branch. Think about migration to spring-cloud based version 2.0.
Legacy micro-infra-spring version is released manually using micro-common-release mechanism. Before you start releasing make sure you are a member of 4Finance organization in GitHub and Bintray. To make release execute:
git checkout legacy
git pull
./gradlew release -Prelease.localOnly -PlocalRelease
./gradlew finalizeRelease -PlocalRelease
./gradlew publishUploadedArtifacts -PlocalRelease
In case of problems with password protected SSH key in step finalizeRelease it can be done manually with:
./gradlew bintrayUpload -PlocalRelease
git push --follow-tags
In case of problems with publishing artifacts (step publishUploadedArtifacts) it can be done manually form Bintray 4finance/micro by clicking on Publish button.
For more details see micro-common-release wiki#manual-release
The person triggering a release should also create a release notes using GitHub interface (manually due to #12).