What have I missed?

[petsan76]

What have I missed here? :)

1. Version in PTE app.json is "version": "26.0.2.0", this is also pushed to main-branch (see attached image). CI/CD build successful! :)
   

2. Create release with version 26.0.2 (see attached image). Successful! :)
   

3. Publish to environment UAT (see attached image). Successful! :)
   

4. The PTE published in UAT now has version 26.0.84.0 (see attached image), where does this version come from??? :)
   

Thank you in advance! :)

Kind regards,
Peter Sandelin
Niedall AB

[nickgoddard777]

This is to do with the chosen versioning https://github.com/microsoft/AL-Go/blob/main/Workshop/Versioning.md.
If you haven't specified this then the default versioning is 0.
This means that you control the Major and Minor version (the first 2 parts of the number). The Build and Revision (3rd and 4th parts) are set by AL-Go Build is GitHub Run Number and Revision is the GitHub Run Attempt minus 1 i.e. the first attempt is 0.
So in your example you have had 84 runs and the artifact was created on the first attempt.
Looking at the documentation I linked above if you want to also control the Build part you can use VersioningStrategy 3, add "VersioningStrategy": 3 to the relevant setting.

[petsan76]

@nickgoddard777 If we want to handle versioning manually, what is the correct settings and options we should change or choose? I now added "VersioningStrategy": 3 to .AL-Go\settings.json :)

1. Set version in app.json, example 26.0.2.0, and push to main-branch
2. Create realase for version 26.0.2 (no check in "Skip updating dependency version numbers in all apps", "Direct Commit?" or "Use GhTokenWorkflow for PR/Commit?")
3. Publish to envitonment for version 26.0.2
4. Result should be our PTE published in envoronment with version 26.0.2.0

Thanks in advance! :)

Kind regards,
Peter Sandelin
Niedall AB

[mazhelez]

Having static app version as you want isn't currently supported by AL-Go.
Here's more info about the supported versioning stategies: http://aka.ms/algosettings#versioningStrategy

[petsan76]

@mazhelez We have a customer that runs AL Go! for Github in their development-environment and they have "versioningStrategy": 15, what does this mean? I can't seem to find any documanationen on this? Thanks in advance! // Kind regards, Peter :)

[mazhelez]

It means that the build sections of the version will be max int value and the revision number is the number of the workflow run.

Adding doc in #1766

[nickgoddard777]

@mazhelez We have a customer that runs AL Go! for Github in their development-environment and they have "versioningStrategy": 15, what does this mean? I can't seem to find any documanationen on this? Thanks in advance! // Kind regards, Peter :)

I was told by Freddy on a ticket I had that 15 should only be used for internal workflows such as PR Build, Test Current etc. CI/CD should use one of the documented strategies.

[mazhelez]

That is indeed correct. As the build part is max int, then any other strategy will produce artifacts with lower version (provided the major.minor is the same), and that might cause issues.

[petsan76]

@nickgoddard777 @mazhelez

Just to be sure! I we have "VersioningStrategy": 3 we will control Major.Minor.Build in our app.json and Revision will be set by Github-runner, correct? :)

Thanks in advance! :)

Kind regards,
Peter Sandelin,
Niedall AB

[aholstrup1]

Correct. AL-Go will set the revision to be the run_number of the workflow while leaving the Major.Minor.Build from your app.json.

http://aka.ms/algosettings#VersioningStrategy