Azure image version doesn't match semver

Question

Azure image version doesn't match semver

Yaron Kaikov 1

Hi

I am defining an Azure compute gallery in order to share our custom image with the community. When trying to define the image version, I see it doesn't match semver syntax.
(https://semver.org/)

Any idea how can i overcome this?

1 answer

Your answer

Answer 1

Ravi Kanth Koppala 3,391 Microsoft Employee Moderator

@Yaron Kaikov ,
The version number for an Azure compute gallery image follows a specific format that includes four integer values separated by periods. The format is: {Major}.{Minor}.{Build}.{Revision}.

The Major value is increased when you make incompatible API changes.
The Minor value is incremented when you add functionality in a backwards-compatible manner.
The Build value is incremented when you make backwards-compatible bug fixes.
The Revision value is incremented when you make changes to the image that do not affect the API or functionality, such as updating documentation or modifying the build process.

For example, a valid version number for an Azure compute gallery image might be 1.0.0.0. This indicates that the image is the first version, with no minor or build updates and no revision
updates.

It's essential to follow this versioning scheme when creating an Azure compute gallery image, as it will allow users of the image to understand the level of compatibility and the nature of any changes made.

Yaron Kaikov 1 Reputation point

2022-12-19T07:22:02.937+00:00

@Ravi Kanth Koppala
Thank you for your answer

regarding the Revision value, can I manually set it? The issue is that during our release process we have the first release candidate build, with version: 2.2.0-rc0 and later we will have 2.2.0

So i am trying to find a why to identify those release candidates
Ravi Kanth Koppala 3,391 Reputation points Microsoft Employee Moderator

2022-12-19T09:19:30.283+00:00

@Yaron Kaikov ,
The revision value for an Azure compute image is automatically set by Azure when the image is published. It represents the number of times the image has been updated or republished and is incremented each time it is updated. The revision value is a 4-digit hexadecimal number, which is appended to the end of the version string, separated by a dash.

For example, if the version string for an image is 1.0.0 and the revision value is 0010, the full version would be 1.0.0-0010.

It is impossible to set the revision value for an Azure compute image manually. Instead, you can use the version string to differentiate between different releases of your image, such as release candidates and stable releases.

You could use the version string to differentiate between your release candidates and stable releases. For example, you could use 2.2.0-rc0 for your first release candidate build and 2.2.0 for your stable release.

I hope this helps! Let me know if you have any other questions.
Yaron Kaikov 1 Reputation point

2022-12-19T09:30:38.393+00:00

@Ravi Kanth Koppala

How can I use 2.2.0-rc0 as my version string?
here is the error i am getting

Share via

Azure image version doesn't match semver

1 answer

Your answer