Docker image that can be used to automatically version projects using semantic versioning.
Visit semver.org to read more about semantic versioning.
Versions are being maintained using git tags.
If no git tag is available, the first version update will result in version 1.0.0.
If git tags are available, it will determine whether to do a major, minor, or patch update based on specific merge request labels. The bump-minor and bump-major labels exist to do either a minor or major bump. If a merge request has no labels attached, it will perform a patch update by default.
As stated above, the version update workflow relies on merge request labels to determine the new version. The bump-minor and bump-major labels have been set as global GitLab labels. However, global labels only propogate to groups created after setting a global label. When adding a global label, they do not automatically propogate to existing groups.
If you cannot select the specified labels in your merge request, your group was most likely created before the global labels were defined. Please follow this guide to setup group-specific labels.
Tip: You can use custom labels for minor and major bumps by setting the MINOR_BUMP_LABEL and MAJOR_BUMP_LABEL environment variables. If not set, the default labels bump-minor and bump-major will be used.
To extract the labels from merge requests, we need an API token to access the Gitlab API. Unfortunately, GitLab doesn't yet support non-user specific access tokens.
Ask your GitLab administrator to add a dummy user ${group_name}_npa to GitLab with access only to your project group. Log in with this user, and create a personal access token with api scope access.
Copy the generated API token and keep it available for the next section.
The NPA username and token need to be injected into the version-update container as environment variables. For this, we'll use group-level variables.
Go to your group's variables section under Settings -> CI / CD.
Add the following variables:
| Key | Value |
|---|---|
| NPA_USERNAME | The name of the NPA user created for your group: ${group_name}_npa |
| NPA_PASSWORD | The personal access token with API scope generated for the NPA user |
| REQUESTS_CA_BUNDLE | The file path to your CA certificate. Ex.: "./root-cert.crt" |
The pipeline configuration below will:
- Generate a unique version tag based on git describe
- Update the version for every build on the
masterbranch. - Tag the docker image built with the updated version as
latestonly fortagbuilds.
This pipeline omits steps for building the project and pushing the resulting Docker image to the registry.
stages:
- generate-env-vars
- version
- tag-latest
variables:
IMAGE_NAME: $CI_REGISTRY/$CI_PROJECT_NAMESPACE/$CI_PROJECT_NAME
generate-env-vars:
stage: generate-env-vars
script:
- TAG=$(git describe --tags --always)
- echo "export TAG=$TAG" > .variables
- echo "export IMAGE=$IMAGE_NAME:$TAG" >> .variables
- cat .variables
artifacts:
paths:
- .variables
version:
stage: version
image: mrooding/gitlab-semantic-versioning:1.0.0
script:
- python3 /version-update/version-update.py
only:
- master
tag-latest:
stage: tag-latest
image: docker:18.06.1-ce
before_script:
- source .variables
script:
- docker pull $IMAGE
- docker tag $IMAGE $IMAGE_NAME:latest
- docker push $IMAGE_NAME:latest
only:
- tag
The new version will be determined based on the commit message. GitLab will automatically format a merge request commit message if the 'Squash commits when merge request is accepted` checkbox is checked during merge request creation.
This workflow relies on that commit message format and will fail the pipeline if it cannot extract the merge request id from the commit message.
Unfortunately, GitLab doesn't yet allow for setting the checkbox to checked by default. Until implemented, make sure to manually check the squash option upon creation.
As described above, if you want to perform a minor or major update, don't forget to add the appropriate label to your merge request.