Hello.
Any suggestions on this?
I have some ideas, but they are all workarounds.
One approach is to use the same process, configuring it differently on 2 server types:
1 - ProcesstA (TST machines)
2 - Approval_Process
3 - ProcessA (PRD machines)
Using this approach is not linking deployments for different environments, because they are both on the same deployment plan and use a process from the same (Release Automation) environment.
Another approach is to add an approval process on the Pre-Deployment section for each environment.
This approach is simpler and provides control, but it does not provide (direct) synchronization between environments.
The last approach I present to you is externalizing the synchronization between environments using a file, database object or change management system that the first deployment should update and the second one should query.
Can anyone suggest a better (or, at least, different) approach?
Best regards,
Ricardo Bernardino