22-07-2021
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
In our current process we are developing in sprints and deploying daily to an AMS environment where our QA is testing. At the end of the sprint we are deploying to a different AMS environment which is used by an external company to test the new release. Some days before the production deployment we are also deploying to an additional environment that is used for integration testing. This environment is also used by the external QA company, but mostly by outside people to test various integrations.
Deployment to these two environments must be coordinated and aligned with all the external users. Since the execution times of the Cloud Manager pipelines vary greatly, especially recently, a fairly large maintenance window must be used. However, a large maintenance window is problematic to coordinate with so many stakeholders. It also starts to impact the amount of tests that can be run on the environments.
Therefore, an approval step before the actual deployment to the dev or stage environment would be very helpful. You could then start the pipeline in the morning, for example, and the deployment would be ready at the agreed time. The maintenance window could then be relatively fixed and small, and it would also no longer be so tragic if something is restarted within the pipeline and the execution time increases.
In principle, the manual approval step for code quality issues already offers something like this, but we do not want to commit major code issues in the software release as a workaround only.