How to update build number in Azure DevOps pipeline?

Azure DevOps Pipelines are an essential part of any software development process. They allow you to build, test, and deploy your application automatically, providing you with a continuous integration and deployment (CI/CD) solution that ensures your code is always up-to-date and ready to be shipped.

One crucial element of any build process is the build number. This number uniquely identifies each build, making it easy to track changes and ensure that you're always using the latest version of your software. In this blog post, we'll take a look at the command to update the build number on an Azure DevOps Pipeline.

What is the Build Number?

The build number is a unique identifier for each build that's created in your pipeline. It's typically a combination of the pipeline name and a unique number that increments with each build. The build number is essential for tracking changes and ensuring that you're always using the latest version of your software.

Why Update the Build Number?

There are many reasons why you might need to update the build number in your Azure DevOps Pipeline. For example, if you're making changes to your codebase, you'll want to create a new build that reflects those changes. Alternatively, if you're deploying your application to multiple environments (such as staging and production), you'll need to update the build number each time you deploy.

The Command to Update the Build Number

Updating the build number in your Azure DevOps Pipeline is a straightforward process that can be accomplished using the ##vso[build.updatebuildnumber] command. This command allows you to set the build number to a specific value or to use a format string to generate a new build number automatically.

Here's an example of how to use the ##vso[build.updatebuildnumber] command to set the build number to a specific value:

##vso[build.updatebuildnumber]NewBuildNumber

In this example, NewBuildNumber is the new build number that you want to use. Replace this value with the build number that you want to use for your pipeline.

Alternatively, you can use a format string to generate a new build number automatically. Here's an example:

##vso[build.updatebuildnumber]$(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)

In this example, the build number is generated using a format string that includes the pipeline name ($(BuildDefinitionName)), the current date ($(Date:yyyyMMdd)), and a revision number ($(Rev:.r)). The revision number is automatically incremented with each new build, ensuring that each build has a unique identifier.

Conclusion

Updating the build number in your Azure DevOps Pipeline is a simple process that can be accomplished using the ##vso[build.updatebuildnumber] command. Whether you're making changes to your codebase or deploying your application to multiple environments, keeping your build numbers up-to-date is essential for tracking changes and ensuring that you're always using the latest version of your software.