Multi Version Build

[Fabianomega]

Hey,

Is it possible to build more than one version?

We need to build every major version of BC from BC23 up to the current version.
Also, the preprocessor symbols need to change during the process.

Is there already a way to make this work?
If not, how can I implement it?

Thanks.

[aholstrup1]

Yeah, that should be possible. You can combine build modes (http://aka.ms/algosettings#buildModes) with conditional settings (http://aka.ms/algosettings#conditional-settings) to accomplish this I would think. Every major version would be a build mode. Then you can add a setting for preprocessor symbols that is conditional on the build mode.

If you need inspiration, you can look at BCApps (https://github.com/microsoft/BCApps/blob/main/build/projects/Apps%20(W1)/.AL-Go/settings.json) where we have a build mode per country and therefore each build mode has its owning country setting.

[Fabianomega]

I have found out that the only version that is not working is BC25.

BC 26 and BC27 is working and i removed the applicationDependency setting in settings.json.

But didnt get the same error as before but the error is still only in BC 25

Installed Apps
Compiling apps
Files in build artifacts folder:
Run-AlPipeline Telemetry Correlation Id: 8563870f-9aca-4e55-a04c-c4f13da250eb
failed to connect to the docker API at npipe:////./pipe/dockerDesktopWindowsEngine; check if the path is correct and if the daemon is running: open //./pipe/dockerDesktopWindowsEngine: The system cannot find the file specified.
failed to connect to the docker API at npipe:////./pipe/dockerDesktopWindowsEngine; check if the path is correct and if the daemon is running: open //./pipe/dockerDesktopWindowsEngine: The system cannot find the file specified.
Enabling Microsoft telemetry...
Error: Unexpected error when running action. Error Message: App generation failed, StackTrace: bei Compile-AppWithBcCompilerFolder, C:\ProgramData\BcContainerHelper\6.1.11\BcContainerHelper\CompilerFolderHandling\Compile-AppWithBcCompilerFolder.ps1: Zeile 520 <- bei , C:\ProgramData\BcContainerHelper\6.1.11\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: Zeile 1171 <- bei , C:\ProgramData\BcContainerHelper\6.1.11\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: Zeile 2234 <- bei , C:\ProgramData\BcContainerHelper\6.1.11\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: Zeile 1739 <- bei , C:\ProgramData\BcContainerHelper\6.1.11\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: Zeile 1734 <- bei , C:\ProgramData\BcContainerHelper\6.1.11\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: Zeile 1285 <- bei Run-AlPipeline, C:\ProgramData\BcContainerHelper\6.1.11\BcContainerHelper\AppHandling\Run-AlPipeline.ps1: Zeile 1270 <- bei , C:\Users\Administrator\Desktop\runner\actions-runner2_work_actions\microsoft\AL-Go-Actions\v8.1\RunPipeline\RunPipeline.ps1: Zeile 477 <- bei , C:\Users\Administrator\Desktop\runner\actions-runner2_work_temp\1fc5e359-06c4-49a0-836c-be023b1a80ef.ps1: Zeile 3 <- bei , C:\Users\Administrator\Desktop\runner\actions-runner2_work_actions\microsoft\AL-Go-Actions\v8.1\Invoke-AlGoAction.ps1: Zeile 21 <- bei , C:\Users\Administrator\Desktop\runner\actions-runner2_work_temp\1fc5e359-06c4-49a0-836c-be023b1a80ef.ps1: Zeile 2 <- bei , : Zeile 1
Error: Process completed with exit code 1.

[aholstrup1]

It's rather limited what I can see from this but "App generation failed" sounds like there is a compilation issue with the app. Hopefully somewhere in your logs you should be able to see what those compilation issues are.

[Fabianomega]

Ok i think i know the problem.

The runtime version is automatically set to the highest Major version:
As descriped in the Docs:

In an absence of runtime specified, the compiler will generate the extension with the highest available major version. Learn more in Choosing Runtime Version in AL.

I think the Problem is when i compile the App Against 25.2 the runtime gets automaticaly set to 14.0. But i need 14.2 for featuers like 'GetRessourceAsText'

Do you know a way how i can manage the runtime version in ALGO

[aholstrup1]

I don't think AL-Go has a built-in way of managing runtime versions. Not that I'm aware of at least.

AL-Go has a setting that lets you control which compiler vsix is used (https://aka.ms/algosettings#vsixfile). We also have a number of script overrides that you can use (https://aka.ms/algosettings#run-alpipeline-script-override) e.g. PreCompileApp. If none of those options work, you may have to hardcode the runtime id 🤷‍♂️

[Fabianomega]

I have another Question?

My builds or now working. I just set the runtime to the lowest supported version i have.

Now i have the Problem that i dont have a "Default" Build Mode so whenever i want to Run the Release Action i get an error that my branch is not up to date with CI/CD

is there a possibility that all Build Modes get put inside one folder that gets regognized right for the release action