Working with a customer right now and trying to accomplish a number of tasks. First, is getting them accustomed to an enterprise branching strategy. The second, is helping them become familiar with Azure DevOps and configuring some build and deployment pipelines. The customer has their own versioning strategy – different across multiple projects – and they communicate with the business stakeholders features and resolved bugs in each release. Using a “one-size-fits-all” versioning configuration doesn’t work, and Azure DevOps only allows for a few custom placeholders in the Build Number. Luckily, Git-flow allows you to tag merges with custom versions so I simply had to configure Azure DevOps to use the latest tag on the master branch for the build number.
Subscribe to receive new posts in your inbox.