Versioning & Deployment

Versioning

Versioning is automated with help from GitHub Actions, semantic-release and the Git-flow branching Model.

Branches

According to Git-flow we have the following permanent branches with special roles:

• develop: Reflects the current development status. Feature branches are created from this and merged back to it, when complete.
• release: Reflects the current testing status. When a stable state is reached on develop branch, it can be merged to release. This will result in creating a release candidate.
• main: Reflects the current productive status. When a release candidate is well tested, it can be merged (from release) to main. This will result in creating a productive release. Furthermore hot fix branches can be created from the main branch, when critical bugs have to be fixed. After merging them back to main they should be also merged back to release and develop.

Determining version string

Publishing

The services / deployment units are bundled as docker images and uploaded to a public docker hub repository with name inoeg. This publishing process is triggered by merging / pushing commits to the special branches mentioned above.

Deployment

Deployment is automated with help from GitHub Actions, Maven, Docker and Watchtower.