![]() Highlighted tags mark currently developed version. changes from release and hotfix branches are merged back to develop.hotfix branches are created from release branches as needed.Release branch will eventually hold released software version release branches are created from develop to finalize release preparation (QA, bug fixes etc…).develop branch holds code for next planned release.Different branching models will work but for sake of our example let’s consider the following model: Requires as few human actions as possible (ideally once per release)įor automated versions generations we’ll use strategically placed Git tags.Generation process is independent of programming language or build system.Our end-goal is to have automatically generated version numbers that: Why not let our CI/CD handle that automatically? Today we’ll see how to automate version number generation using Git tags and TeamCity dynamic build numbers. Sometimes it’s manually assigned by development team, sometimes it’s managed by the build system, sometimes taking Git commit hash or combination of any above methods. What version number schema to choose ? How to assign version numbers ? What about snapshots ?Įach mature enough project had that issue solved at some point. When done manually it’s mundane task, often confusing and prone to errors.Īt the beginning of each project there is always a issue of software version numbers. One of such tasks is maintaining software version numbers. Nobody likes boring and repeatable tasks, that’s why we want to automate them as much as possible.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |