Release Gate

A lifecycle defines the path to production for a specific type of release. A lifecycle is made up of phases through which software changes need to progress before final release and expresses quality requirements which software changes must meet before deployment to an environment.

Quality Status

Development, test, and operations teams may assign quality statuses to an application version to notify stakeholders to indicate that version has met specific quality requirements. Those statuses can be applied manually in the tool or through an integration with an external system, such as a REST API call or a deploy plug instep. By integrating with other quality tool UrbanCode Release provides a repository for quality results coming from many different testing groups, phases of testing, and testing tools. For example, you can see integration testing results, automated UI testing, security, and performance testing all in a single view.

Gates enforce quality controls and provide an audit trail

Scheduled deployments which do not meet gate criteria are flagged with gate failure icons. Schedule deployments where the gate criteria are unmet are prevented from starting, enabling process enforcement. In UrbanCode Release, you can drill down into the scheduled deployment detail to see where an application version is not meeting the gate criteria and why. It is also possible for a user with sufficient privileges to grant a temporary exception.

Supports Continuous Delivery across Multiple applications

Once a lifecycle has been defined and an automated deployment plan put in place, it is possible to implement an auto progression of application versions through the environment pipeline for continuous delivery scenarios. (View more here)

4