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
172
stars
37
forks
source link
Build Tool task "Power Platform Copy Environment" shows success when copy fails, or shows failure when copy succeeds #949
We are using the Copy Environment task in our ALM pipeline built on ALM Accelerator. Intermittently, we will have successful pipeline runs to create the UAT environment, but a subsequent failure when trying to import the solution upgrade. Looking back at the Pipeline run, we can see that the Build Tool task succeeded, when in PPAC it shows that the copy failed:
Conversely, we've also had copy operations succeed in PPAC, but appear as failed in the Build Tools task:
We are using the Copy Environment task in our ALM pipeline built on ALM Accelerator. Intermittently, we will have successful pipeline runs to create the UAT environment, but a subsequent failure when trying to import the solution upgrade. Looking back at the Pipeline run, we can see that the Build Tool task succeeded, when in PPAC it shows that the copy failed:![image](https://github.com/microsoft/powerplatform-build-tools/assets/106766774/66c41d18-52d5-47aa-ac81-4f7a96166726)
Conversely, we've also had copy operations succeed in PPAC, but appear as failed in the Build Tools task:![image](https://github.com/microsoft/powerplatform-build-tools/assets/106766774/0b777499-cbea-4fd4-957d-358034e68957)
YAML task:![image](https://github.com/microsoft/powerplatform-build-tools/assets/106766774/feb5104c-7a15-4c95-b664-046106f51c0c)