[Bug]: workspaceCompilation not working with trustedNuGetFeeds (external NuGet dependencies)

[GHofstadter]

AL-Go version

AL-Go version: v9.1

Describe the issue

When workspaceCompilation is enabled, the build fails with AL1022 for external AL app dependencies that are sourced from trustedNuGetFeeds. The same repository builds successfully when workspaceCompilation is disabled.

This is related to #2214, which fixed the same symptom for appDependencyProbingPaths. However, the fix in PR #2217 did not cover the trustedNuGetFeeds code path. NuGet packages are not copied into the compiler's symbols folder before altool.exe workspace compile is invoked, so the compiler cannot find them.

Expected behavior

successful build with enabled the workspaceCompilation and trustedNuGetFeeds

Steps to reproduce

• Configure trustedNuGetFeeds pointing to a third-party NuGet feed
• Add a dependency in app.json to a package available on that feed
• Enable workspace compilation: "workspaceCompilation": { "enabled": true }
• Run CI/CD

Additional context (logs, screenshots, etc.)

to reduce the build time in a multi-project, I enabled the workspaceCompilation

[Alexander Holstrup (aholstrup1)]

Unfortunately, trustedNugetFeeds is not supported for workspace compilation at the moment. This is one of the reasons we've currently marked it as Preview in the documentation (http://aka.ms/algosettings#workspaceCompilation). We are still working on getting the last few pieces into place before taking it out of preview :) I'll see if I can add something to our docs to make this clearer.

For now, if you rely on trustedNuGetFeeds for dependency resolution you should use the useCompilerFolder setting instead to do container-less compilation.

[GHofstadter]

Thx for your feedback. I already us useCompilerFolder (doNotPublishApps: true), it takes ~5 min for each App to be build. Since I have up to 5-10 apps it sums up to 25 min. I tried to optimize as much as possible, but could not get a shorter build time.

Therefore, is there any hope to get support for trustedNugetFeeds, too (when it is out of preview)?

Thx Alexander Holstrup (@aholstrup1)

[Alexander Holstrup (aholstrup1)]

5 minutes per app to compile? 🤔 Are you compiling all 5 apps in the same job or in separate jobs?

Therefore, is there any hope to get support for trustedNugetFeeds, too (when it is out of preview)?

Yeah, that is the plan :) That is very much a feature we would like to support. I just need to find the time to get the final bits done and ready :)

[GHofstadter]

Sorry, i was not specific enough:
The Build step take ~5 min for each App (the compilation itself ~ 1 min).
The Apps are build in separate jobs, but since they have dependency the have to be build one after the other.

[Alexander Holstrup (aholstrup1)]

The Build step take ~5 min for each App (the compilation itself ~ 1 min).

Mmh right... And presumably the other 4 minutes are mostly spent on downloading the artifact and making the compilerFolder?

The Apps are build in separate jobs, but since they have dependency the have to be build one after the other.

Got it... So it's 1-2 apps per job, split out over 5 jobs that run sequentially?

[GHofstadter]

Alexander Holstrup (@aholstrup1)

You got it correctly, see
https://drschaer-my.sharepoint.com/:i:/p/guenther_seeber/IQDy_tecUb30QrEwX7LBofVSAd13PWRI3NjY6NMePovcnEQ?e=Je6Tep

[Alexander Holstrup (aholstrup1)]

I'll move this to an idea for now, since it is a known limitation. One that we want to fill in relatively soon :)

[GHofstadter]

Alexander Holstrup (@aholstrup1)

We are planning to migrate to GitHub Enterprise (GHE). At the moment, the remaining major concern is the performance gap compared to our current setup.

Therefore, I would like to ask whether there is already a roadmap or estimated timeline for supporting workspace compilation with trustNuGetFeed in a future release. This feature could significantly improve our build performance and would be an important factor in our migration planning.

Any information you can share regarding its availability or prioritization would be greatly appreciated.

[Alexander Holstrup (aholstrup1)]

GHofstadter

We are planning to migrate to GitHub Enterprise (GHE)

Note that this isn't something we officially support in AL-Go for GitHub. Not yet at least 😄
#1999

Any information you can share regarding its availability or prioritization would be greatly appreciated.

It is something I am working on right now but it's hard to share an exact date as we have to prioritize it against other things. I hope to have something ready in the next month or two, but I can't make any promises unfortunately 😐