Statuses indicate application deployment readiness. You
can track the readiness of an application version for deployment by
tracking the requirements for application versions with statuses.
When you setup a lifecycle for a release you can attach gates with
statuses to phases in the lifecycle. Each phase can have one or more
gates. A gate represents a requirement and status indicates that
the requirement has been met. A requirement can be the completion
of a testing activity or an approval. When the requirement is met
for the application, you can grant status to an application to indicate
that the application meets the requirement. An application version
can have multiple different statuses. You can determine whether the
application is ready for deployment by inspecting application statuses.
For example, a project lifecycle has the following phases: automated
testing and performance testing phase. The entrance requirements to
the performance testing phase might be completion of build verification
testing, passing a JUnit test, and receiving approval from the quality
assurance lead. To represent this scenario, you can define a gate
in the performance testing phase with these statuses:
- Build verification test pass
- JUnit test pass
- Quality assurance lead approval
The application is ready to move to the performance testing phase
when it achieves all three statuses or when it has exemptions for
the missing statuses.
You can schedule a release for deployment when all application
versions that are assigned to that release have every required status
by the phase to deploy, or the missing statuses have exemptions. If
some statuses are missing and do not have exemptions, the gate fails,
and the deployment is blocked.
Tips: - Statuses come from integration with IBM® UrbanCode Deploy,
or you can manually create a status. To create a status, click Release
Process and then go to the Quality Statuses tab.
Then, click Add New, and complete the details.
- Gates must have at least one status. To add a gate with statuses
to a phase, click Release Process, and then
click a lifecycle. Then, click Add Gate, select
a status, and click Save. Repeat these steps
for all the statuses to add.
- To grant a status to an application version, click Applications.
Then, click an application version, and add the status to an application
version in the Quality Statuses column. You
can double-click the status to edit status details such as comments
and attachments.
To run a deployment with an application that is missing statuses,
you can create an exemption. To create an exemption, click Releases &
Deployments and click a release. Then, click Details for
an application with failed gate status. Next, click Create
Exemption, and complete the details.