Artifact Versioning and Publishing Example

Structured Git versioning using Semantic Versioning

In a traditional semantic versioning scheme, there exists a standard pattern of versioning:

MAJOR.MINOR.PATCH

gradle-semantic-release-plugin uses this strategy to apply to Git commits

Here are ways to apply a version update on each commit

If a commit starts with:

• fix(..) --> bumps PATCH
• docs(..) --> skips github release, but creates a SNAPSHOT of the next PATCH version

Full list of conventions

Publishing source releases to GitHub

You must export GH_TOKEN environment variable to your environment with a GitHub token as the value to be able to use the release task.

TravisCI

Add the GH_TOKEN variable to your TravisCI pipeline.

On every push to the master branch, a release will take place.

Refer to .travis.yml file on how to create a TravisCI pipeline configuration.

Example Workflow using TravisCI

1. On develop, add commits as per development flow. Semantic Release will not release on develop
2. Each commit should follow the convention outlined here
3. When ready to create a release, switch to master and merge all commits from develop and push!
4. On master, TravisCI will build the branch and trigger release which will cut SNAPSHOT into a release version.
5. release will also create a release artifact in Releases
6. release will also create a tag with the released version.