Skip to content

How to release a new version (old)

Kevin Wallimann edited this page Mar 14, 2024 · 1 revision

Release with TeamCity

Manual part

  1. Create a release branch, e.g. release/0.5.6
  2. Push all changes you want to release to that release branch.
  3. Change the version in pom if needed. Current version without -SNAPSHOT will be used as next version (e.g. 1.0.3-SNAPSHOT will be released as 1.0.3).
  4. Run Hyperdrive-Trigger - Release job in TeamCity on release/0.5.6 branch

Automatic part

TeamCity will

  1. release: create release commit and tag, and push them to release branch
  2. deploy: once the tag is created two jobs (for Scala 2.11 and 2.12) will be triggered that will build and deploy Abris into Maven repo.

Manual part

  1. Go to https://oss.sonatype.org/#stagingRepositories. Find zacoabsa-.... Release or drop the artefacts.
  2. Merge the release branch into develop and delete the release branch.

Manual release on laptop

  1. Merge all changes into develop.
  2. git checkout -b release/<version>, e.g. git checkout -b release/1.0.0
  3. mvn -Dmanual-release -B release:prepare Will push branch and tag to github. The version will be inferred from the current SNAPSHOT version. If you want to manually specify a version, use -DreleaseVersion=1.0.0. This step produces a backup file of pom.xml and a release.properties file.
  4. git clean -f to remove the backup files
  5. git checkout v<version>. Checkout the tag
  6. mvn -B -e -DskipTests -Dmanual-release -Ddeploy -Dossrh clean deploy Build project and deploy to ossrh. Deployment to ossrh may take up to 20 minutes.
  7. Go to https://oss.sonatype.org/#stagingRepositories. Find zacoabsa-.... Release or drop the artefacts.
  8. Merge the release branch into develop and delete the release branch.
Clone this wiki locally