Closed Arthurvdv closed 11 months ago
Seems to be a temporary issue indeed. for the time being, you can remove the "latest" part, so it will grab it from the artifacts?
.. which will break the custom codecops .. 🤔
.. which will break the custom codecops .. 🤔
That's indeed the sole reason for setting the "latest". For now we'll set the artifactversion to 22.5 so we have a workaround.
The versions are there, but probable still marked as pre-release I guess?
Issue has been resolved
*** Fetching LATEST VSIX from Marketplace
*** Fetching Alternative VSIX: [https://ms-dynamics-smb.gallerycdn.vsassets.io/extensions/ms-dynamics-smb/al/12.0.875970/1696255960002/Microsoft.VisualStudio.Services.VSIXPackage]
*** Downloading Extension from...[https://ms-dynamics-smb.gallerycdn.vsassets.io/extensions/ms-dynamics-smb/al/12.0.875970/1696255960002/Microsoft.VisualStudio.Services.VSIXPackage]
Invoke-RestMethod -Method Get -Uri "[https://ms-dynamics-smb.gallerycdn.vsassets.io/extensions/ms-dynamics-smb/al/12.0.875970/1696255960002/Microsoft.VisualStudio.Services.VSIXPackage"](https://ms-dynamics-smb.gallerycdn.vsassets.io/extensions/ms-dynamics-smb/al/12.0.875970/1696255960002/Microsoft.VisualStudio.Services.VSIXPackage%22) -OutFile "C:\vsts-agent-alops-warp10\_work\_temp\VSIX\custom.vsix"
Describe the bug With the release of version 23 of Business Central the ALOpsAppCompiler@2 step fails.
The problem seems to be the "Fetching LATEST VSIX from Marketplace", where this returns the v11.7 in stead of v12. With some luck it will resolve itself in the next couple of hours?
the used yaml
the output