Creating and assigning quality statuses
Apply quality statuses to applications and phases to ensure that they meet the criteria you set. Determine whether an application is ready to deploy by monitoring the statuses that are applied to an application version.
You define quality statuses to reflect the criteria that you require in your release process. A criterion can be the completion of a testing activity or the completion of a review process. When the application version meets the criteria, you apply the status to it. If your release process requires an application to meet multiple criteria, you can apply multiple quality statuses to the application version. Then, you can determine whether the application is ready for deployment by inspecting application statuses.
You use gates to control the progression of a release through its lifecycle phases by adding gates to phases. The application version must contain all the quality statuses that are included in a gate before it can enter that phase. For example, an application might have to pass a set of tests before it enters a quality assurance phase or receive a quality check before it enters production.
You can create quality statuses and apply them to application versions in IBM® UrbanCode™ Release. You also can create snapshot statuses, apply them to application snapshots in IBM™ UrbanCode Deploy, and import the snapshot statuses into IBM UrbanCode Release.