yrtimid / azure-pipelines-semver-bump

Semantic version bump task for Azure DevOps Pipelines

Semantic Version Bump

Azure DevOps Pipelines task for Builds and Releases

Bumps (increments) version saved in an environment variable.

Wraps well known node-semver library inc() function.

Usage

• Define and populate variable which will hold a version
• Add a task to your pipeline
• Put the name of your version variable into "Version variable name" field
• Select desired "Increment level"
• Optionally: change "pre id" prefix

Version value is read from the configured environment variable, incremented accordingly and written back to the same variable.

❗ Important to understand: Azure DevOps Pipelines environment variables exists only during pipeline run and destroyed when finished. There is no way of persisting variable value between runs.

To continuosly increment the version its value should be persisted anywhere after increment and reloaded on next run.
Some possible technics (for example, out of scope of this task):

• Commit as file directly to version control
• Save as artifact and get value from "last successful build"
• Discover last version from artifactory

azure-pipelines-semver-bump's Issues

Does not increase version

Good day! I use it in TFS, the problem is that it does not increase the version, I attach the logs.
logs_2219.zip

After task completion variables are not set with newer version

After task completion variables are not set with the newer version. If I rerun newly then it starts from the default number

bump versioning for docker image?

how to do docker image bump versioning

Great Tool

Hi @yrtimiD

Great tool, however we're trying to get this working but it keeps complaining about:

##[error]Can't increment version: Error: Variable "1" doesn't contains anything. Valid version string was expected.

how do I get this to increment the MajorVersion?
what is needed to put into the Version variable name?

below is my current pipeline setup:

build pipline:

variables: