Fix build error when using versioningStrategy 3+16

Actions/AL-Go-Helper.ps1

@@ -1462,7 +1462,7 @@ function CreateDevEnv {
         }
 
         if ($settings.versioningStrategy -eq -1) {
-            if ($kind -eq "cloud") { throw "Versioningstrategy -1 cannot be used on cloud" }
+            if ($kind -eq "cloud") { throw "versioningStrategy -1 cannot be used on cloud" }
             $artifactVersion = [Version]$settings.artifact.Split('/')[4]
             $runAlPipelineParams += @{
                 "appVersion"  = "$($artifactVersion.Major).$($artifactVersion.Minor)"
@@ -1471,13 +1471,24 @@ function CreateDevEnv {
             }
         }
         else {
+            $appBuild = 0
+            $appRevision = 0
             if (($settings.versioningStrategy -band 16) -eq 16) {
+                # For versioningStrategy +16, the version number is taken from repoVersion setting
+                $repoVersion = [System.Version]$settings.repoVersion
+                if (($settings.versioningStrategy -band 15) -eq 3) {
+                    # For versioning strategy 3, we need to get the build number from repoVersion setting
+                    if ($repoVersion.Build -eq -1) {
+                        Write-Host "WARNING: RepoVersion setting only contains Major.Minor version. When using versioningStrategy 3, it should contain 3 digits"
+                    }
+                    else {
+                        $appBuild = $repoVersion.Build
+                    }
+                }
                 $runAlPipelineParams += @{
-                    "appVersion" = $settings.repoVersion
+                    "appVersion" = "$($repoVersion.Major).$($repoVersion.Minor)"
                 }
             }
-            $appBuild = 0
-            $appRevision = 0
             switch ($settings.versioningStrategy -band 15) {
                 2 {
                     # USE DATETIME

Actions/RunPipeline/RunPipeline.ps1

@@ -292,8 +292,18 @@ try {
         $appRevision = $artifactVersion.Revision
     }
     elseif (($settings.versioningStrategy -band 16) -eq 16) {
+        # For versioningStrategy +16, the version number is taken from repoVersion setting
+        $repoVersion = [System.Version]$settings.repoVersion
+        if (($settings.versioningStrategy -band 15) -eq 3) {
+            # For versioning strategy 3, we need to get the build number from repoVersion setting
+            $appBuild = $repoVersion.Build
+            if ($appBuild -eq -1) {
+                Write-Host "WARNING: RepoVersion setting only contains Major.Minor version. When using versioningStrategy 3, it should contain 3 digits"
+                $appBuild = 0
+            }
+        }
         $runAlPipelineParams += @{
-            "appVersion" = $settings.repoVersion
+            "appVersion" = "$($repoVersion.Major).$($repoVersion.Minor)"
         }
     }
 

RELEASENOTES.md

@@ -1,7 +1,11 @@
-## AL-Go Telemetry updates
+### AL-Go Telemetry updates
 
 AL-Go telemetry now includes test results so you can more easily see how many AL tests, Page Scripting tests and BCPT tests ran in your workflows across all your repositories. Documentation for this can be found on [this article](https://github.com/microsoft/AL-Go/blob/main/Scenarios/EnablingTelemetry.md) on enabling telemetry.
 
+### Issues
+
+- Issue 2055 When using versioningStrategy 3+16, you get an error when building
+
 ## v8.1
 
 ### Custom AL-Go files

Scenarios/settings.md

@@ -37,7 +37,7 @@ When running a workflow or a local script, the settings are applied by reading s
 | Name | Description | Default value |
 | :-- | :-- | :-- |
 | <a id="country"></a>country | Specifies which country this app is built against. | us |
-| <a id="repoVersion"></a>repoVersion | RepoVersion is the project version number. The Repo Version number consists of \<major>.\<minor> only and is used for naming build artifacts in the CI/CD workflow. Build artifacts are named **\<project>-Apps-\<repoVersion>.\<build>.\<revision>** and can contain multiple apps. The Repo Version number is used as major.minor for individual apps if versioningStrategy is +16. | 1.0 |
+| <a id="repoVersion"></a>repoVersion | RepoVersion is the project version number. The Repo Version number consists of \<major>.\<minor> only (unless versioningStrategy is 3, then it should contain \<major>.\<minor>.\<build>) and is used for naming build artifacts in the CI/CD workflow. Build artifacts are named **\<project>-Apps-\<repoVersion>.\<build>.\<revision>** and can contain multiple apps. The Repo Version number is used as major.minor for individual apps if versioningStrategy is +16. | 1.0 |
 | <a id="projectName"></a>projectName | Friendly name for an AL-Go project to be used in the UI for various workflows (CICD, Pull Request Build, etc.). If not set, the name for the project will be the relative path from the root of the repository. | '' |
 | <a id="appFolders"></a>appFolders | appFolders should be an array of folders (relative to project root), which contains apps for this project. Apps in these folders are sorted based on dependencies and built and published in that order.<br />If appFolders are not specified, AL-Go for GitHub will try to locate appFolders in the root of the project. | [ ] |
 | <a id="testFolders"></a>testFolders | testFolders should be an array of folders (relative to project root), which contains test apps for this project. Apps in these folders are sorted based on dependencies and built, published and tests are run in that order.<br />If testFolders are not specified, AL-Go for GitHub will try to locate testFolders in the root of the project. | [ ] |