Build an simplistic release pipeline

[tomkerkhove]

Build an advanced release pipeline to automatically release a new version.

Specification

• Build the codebase
• Run unit tests (relates to Introduce unit testing #32)
• Build Docker image
• Tag Docker image for full releases ({major}.{minor}.{patch} & {major}.{minor})
• Tag Docker image for pre-releases ({major}.{minor}.{patch}-{description})
• Push Docker image to Docker Hub for full releases ({major}.{minor}.{patch} & {major}.{minor})
• Push Docker image to Docker Hub for pre-releases ({major}.{minor}.{patch}-{description})
• Create a GitHub release when version is of format {major}.{minor}.{patch}
• Create a GitHub pre-release when version is of format {major}.{minor}.{patch}-{description}

Versioning

Every build is queued by specifying the version to release. This supports the following formats:

• {major}.{minor}.{patch} for full releases
  • Creates a GitHub release
• {major}.{minor}.{patch}-{description} for preview releases
  • Creates a GitHub pre-release

Docker tags

Every release should tag the docker image twice:

• {major}.{minor}.{patch} which is specific for this release
• {major}.{minor} which gives you all the features for this combination, but always pulls in the latest patch version. This should not be done when it is a preview release.

This is important as this enables consumers to always run on the latest bug fixes and most importantly security fixes.

[tomkerkhove]

{major}.{minor} tag was added for full releases. unit tests will be done in v0.5.0

[tomkerkhove]

Pipeline is completed.