search

microsoft / powerplatform-build-tools

Power Platform Build Tools automate common build and deployment tasks related to Power Platform. This includes synchronization of solution metadata (a.k.a. solutions) between development environments and source control, generating build artifacts, deploying to downstream environments, provisioning/de-provisioning of environments, and the ability to perform static analysis checks against your solution using the PowerApps checker service.
MIT License
200 stars 41 forks source link

Publish-pipeline-artifact fails with CLI for managed solution but still okay with Powershell #216

Closed rcatbp closed 2 years ago

rcatbp commented 2 years ago

Pipeline worked for 9 months then upgraded from Power shell to CLI. Now publish only works for Unmanaged but fails for managed I raised a full ticket here https://developercommunity.visualstudio.com/t/Publish-Pipeline-Artifact-Power-Platfor/10170869 If I untick the 'managed' box it worked, how weird is that? Now reverted back to Powershell and all okay but I have no hair left. Cheers, Richard

publish-pipeline-artifact-fails

Summary-Unmanaged-okay-managed-fails.txt

davidjenni commented 2 years ago

@rcatbp Looking at your .txt file, the Publish task fails since it cannot find the just-exported D:\\a\\1\\a\\PADCompliance-Managed.zip file. We had a bug in the underlying pac CLI that resulted for managed exports to add an extra "_managed" to the base name (resulting in your example with this file on disk: PADCompliance-Managed_managed.zip).

The upcoming refresh (ETA later this week) will have this regression fixed; in the meantime, change your "publish managed.zip" task to use either a wild card for the artifact input name, or add the extra _managed, as above.

AB#2925297

davidjenni commented 2 years ago

Fixed with 2.0.8; note that due to Azure DevOps's caching, it might take several hours until all build agents run with the latest update

https://github.com/microsoft/powerplatform-build-tools/releases/tag/v2.0.8

CC: @rcatbp