CODEWITHSUNDEEP
azureazure-devopsazure-pipelines
Ken Bonny
Ken Bonny

Reputation: 789

How to set up automatic nuget version increments

In my release pipeline for a dotnet core project, I want to increment the assembly version automatically so I don't need to update it manually each time. This is so my Nuget version is increased every time.

At the moment I'm using the dotnet pack command and adding the build number at the end using the "Automated Package Versioning" set to "Use Environment Variable: Build.BuildNumber". Then I set the "Option > Build Number Format" to "1.0.$(BuildID)". First, I tried setting the attribute of the .csproj file to 1.0.$(BuildID), but the pipeline did not pick that up.

The problem is that I have to edit my build pipeline every time I want to adjust my major or minor semver version. Yet with the teams, we agreed not to put build pipeline config in source control (yaml files). Is there a way we can put a part of the build pipeline in a yaml file so that we can override parts of the configuration?

For example: I could set the "Build Number Format" to "$(Major).$(Minor).$(BuildID)" and then the partial yaml could override the Major and Minor variables.

Upvotes: 3

Views: 1049

Answers (1)

Leo Liu
Leo Liu

Reputation: 76670

How to set up automatic nuget version increments

If you want to automatic nuget version increments, you could use the BuildNumber $(Rev:r) instead of $(BuildID):

Run (build) number:

$(Rev:r)

2 (The third run on this day will be 3, and so on.)

Use $(Rev:r) to ensure that every completed build has a unique name. When a build is completed, if nothing else in the build number has changed, the Rev integer value is incremented by one.

If you want to show prefix zeros in the number, you can add additional 'r' characters. For example, specify $(Rev:rr) if you want the Rev number to begin with 01, 02, and so on.

So, you could set the Build Number Format to $(Major).$(Minor)$(Rev:.r).

Hope this helps.

Upvotes: 1

Related Questions