Docker build
Setup CI to test and build a Docker image and then publish it to GitLab Registry, and then call a script on beta server to re-deploy it using a preconfigured docker-compose from another project. This should happen on each merge to master. The latest
label should be applied to each new build, as well as current minor version taken from .env file. The versioning strategy should change from the previous 1.0-pre-#
to Semantic Versioning 2.0 (MAJOR.MINOR.PATCH), where developers may only change the PATCH part. The test deployment server may attach the commit short hash to the end separated by a minus, eg. 1.1.4-1f34ae25
meaning "This is a development version of the software on a branch starting from a release where the version was 1.1.5
with the commit hash 1f34ae25
." The version number should be increased to 1.1.5
immediately before submitting a merge request, and only if no branch with version 1.1.5
was merged in the meantime, in which case 1.1.6
should be used, following the same rules.