13. SCD4J Developers

Jump to bottom Edit New page

Simple Continuous Delivery for Java and Groovy Developers edited this page May 16, 2016 · 37 revisions

Steps to Release

Run unit tests
Run a manual test (just in case)

Use uploadArchive gradle task for dev publishing
Use gradle-examples for your manual tests

Execute bintrayUpload gradle task

If everything gonna ok, BINTRAY_DEPLOY_NUMBER will be incremented in version.properties
- Supposed to represent the next scd4j deployment
The generated version will be deployed in Bintray
IMPORTANT: this step requires gradle.properties file with bintray_user and bintray_api_key properties

Wait the new version be published in gradle plugins web site

Relaxe and drink a coffee, it gonna take a while

Run update_scd4j_version.sh 'VERSION_NUMBER' in scd4j-examples dir

This is required to update scd4j version in all example projects and to make sure the examples will be 100% ready to go

If everything goes ok, refresh the workspace, pull, commit and push it to GitHub
Tag the project

The tag name must be the exact version number shown in the logs during bintrayUpload.
The tag description should be a very short description

Go to GitHub and create a new release from the just created tag

Enter the release notes in description

Thanks for the interest of making the software delivery somewhat more professional.