[Bug]: NextMajor (v28) fails when downloading dependencies from NuGet-feed

[peterelmqvist]

AL-Go version

8.2

Describe the issue

When we run NextMajor (v28) and we have a dependency which is fetch from a trustedNuGetFeed we get an error saying "The property 'ServerInstance' cannot be found on this object. Verify that the property exists."

Expected behavior

Expect that the dependency should be downloaded an published to the environment.

Steps to reproduce

I've done a clear repro of this.

• Create a new repository from the AL-Go Template

• Run Create new app

• Run Test Next Major - Success

• Add trustedNuGetFeed
  "trustedNuGetFeeds": [ { "url": "https://nuget.pkg.github.com/directions4partners/index.json" } ]

• Add a dependency
  { "id": "e33746ef-a796-46ca-8a1a-fb3840a42c48", "name": "Cloud Customer Management Solution", "publisher": "Directions for partners", "version": "0.0.2.0" }

• Run Test Next Major - Fails

Additional context (logs, screenshots, etc.)

I've done the repo in a public repository.
https://github.com/peterelmqvist/Test-NuGetDependency

[peterelmqvist]

Any news on this, any more information I can add? We started to execute NextMajor on a schedule today for our customers and everyone with a dependency failed with the same error so this is a real issue for our planning towards v28.

[aholstrup1]

No, I don't think more is needed from you. I was able to repro it quite quickly from the repository you set up, so thank you for that 🙏

Finding the root cause (and a fix for it) has been a bit more difficult. We are looking into it though 👍

[aholstrup1]

@peterelmqvist I've deployed a mitigation to AL-Go preview. Would you be able to test that to verify that it works on your end again?

The root cause isn't fixed, but I was able to get a successful build with this mitigation. The root cause is related to microsoft/navcontainerhelper#4101

[peterelmqvist]

@aholstrup1 I've verified this in our pipelines and this seems to mitigate the issue. Will this be be part of a release soon or should we use preview for now.

[aholstrup1]

Thanks for confirming @peterelmqvist

We just released 8.3 last week so it'll probably be a little while until the next stable version. But let me see if we can't hotfix it to v8.2 and v8.3 instead given that it's a fairly small change.