Maintenance happens. It’s a business necessity – upgrades, patches, security updates, you name it. With the release of UrbanCode Deploy 7.0.3, the product team has added Maintenance Mode functionality to UrbanCode Deploy. This functionality provides a great way to let your end users know maintenance is coming.
When the UrbanCode Deploy server goes into Maintenance Mode, users will see a large banner across the top of the user interface, letting them know the server is in maintenance mode.
All currently running deployments will not be affected, and will be given a chance to run to completion. Sub-processes of existing requests will continue. This ensures that before you bring the server down, you can check to make sure there are no running deployments that might be interrupted.
While in maintenance mode, no new deployments can be started (either through the UI, or via API). New version imports, Auto Discovery, Configuration Compares, and Approvals are also prohibited while in this mode to ensure consistency and resiliency during the outage.
Oftentimes, the deployments that are most affected are the ones that are scheduled during a maintenance outage. In the past, it was on the application teams to be responsible for the outage windows and to know if their deployments were interrupted. Now, once the UrbanCode Deploy server is brought out of Maintenance Mode it will identify all deployments that were scheduled but did not take place due to the outage. The teams associated with these deployments will be conveniently emailed so they are made aware of the situation and can take appropriate action.
Check back next week for the announcement of UrbanCode Deploy 7.0.3.