Hello GitLab Community, I have a question in regards to versioning code. Just looking for ideas on how other teams do this. Right now, it is a very manual process for my team to update the version number in our codebase after a release. Currently we run a script to update the version number in the …

Hey @cbille0 , Yes, everything is done in the CI pipeline. Not every MR necessarily gets an independent release or a tag. However, every build on a release branch does have the potential receive a tag. Here is the basic flow: Build (including unit tests, etc) Integrate (runs appropriate integrat…

I am also quite interested in knowing this. I’m becoming a huge fanatic of CI, but manual versioning is still a bummer - though I confess that I haven’t really looked into the options…

I use git tags. Tag each release with your version number, e.g. ‘v1.0.0’, you can then have a script in your build process that updates the version number in the code based on the current tag, which you can get from the CI_COMMIT_TAG variable ({CI_COMMIT_TAG#v} if you want to exclude the leading ‘v’…

Hello, Thank you for your response. I see what you are saying in regards to tags. When the script runs to update the version in the code, how does the code get committed? I was under the impression it is not a good idea to have your CI/CD pipeline push commits to your repository as it can be dif…

I don’t commit the version back into the repo, just edit whatever files are necessary for the build/deploy process in place then run the build/deploy. The end result is captured as a build artifact or deployed to a server. You can always recreate the same build by re-running the CI job. Here’s an e…

The strategy I’m most fond of uses these principles: The Major.Minor.Patch of semver is committed as source and is updated in standard MR fashion All tags are 100% automatic & done by CI Semver Extraversion is incremented automatically per build. The assigned semver is not commited in the reposito…

Hello, I took at your code. I see what you are doing. I am currently doing the same thing. I have a variable for the version and an arbitrary placeholder value. When I push a tag, I set the version to the tag just like you are doing in your codebase. It seems as though release branches are the…

Hello @hstenzel , Thank you for your response. So when you version code, you have everything done via the CI build process. How does the CI pipeline know when to create a tag? Is this triggered by a MR?

We use tags with pyscaffold for our python packages. Works automatically whenever we do setup.py release.

Versioning code

How to Use GitLab

cbille0 May 19, 2020, 2:46am 11

It certainly does help. Thank you for your response!

-Chris

Topic		Replies	Views
How to version or tag incrementally in Gitlab CI/CD when merging from Production to Release branch GitLab CI/CD ci , runner , merge-requests , docker , pipelines	0	2308	August 27, 2020
Looking for similar feature as Github action's predefined tasks GitLab CI/CD	7	2203	July 23, 2022
Versioning How to Use GitLab	1	673	October 1, 2019
Semantic versioning How to Use GitLab	0	690	July 24, 2020
Semantic Versioning for every pipeline GitLab CI/CD	0	781	August 5, 2023

Versioning code

Related topics