Closed mrmwink closed 3 years ago
Part of the problem is that when you run this from the UI, it submits the job in the background and you aren't always actually waiting for it to complete since the UI times out while it the job still runs to completion. When you run it from a pipeline, it is actually waiting for it to complete. This is important from an automation perspective as the org can't handle another Solution type activity (Import, Upgrade, Publish, etc) while one is running.
That makes sense, I just tried in the UI and then tried to deploy a 2nd solution to the environment and it fell over spectacularly as the first one was running in the background!!
@mattp65 @mrmwink thanks for this. Closing the issue. Please re-open if you have any further questions.
Hi,
I'm currently using the Solution Upgrade using the holding solution and then Upgrade Solution task, which has been working fine but takes much longer as when doing the straight Upgrade available through the UI, the question is can I replicate the straight solution upgrade that is the default option when manually updating through the UI, via a task within the DevOps pipeline!?
Thanks
Mike