Deployment of deployable release trains or parent or standalone
release packages initiates the deployment tasks that you have configured and
You must have completed the configuration for deployment tasks.
It is recommended that you validate the deployment tasks before
beginning the deployment. See
Validating Deployment Tasks.
To run a deployment:
Select the deployable release train or release package you want to
Note: Standalone and parent release packages can be deployed
directly. Child packages are deployed when their parent release package is
Move the item through its lifecycle until the
Start Deploy option is available.
Start Deploy and enter any comments needed in
Message Log field.
The deployment is initiated and execution of associated deployment
tasks is initiated. After any scheduling criteria is met for deployment tasks
and any required approvals are made, the deployment executes each of the
deployment tasks in the order specified.
When you initiate deployment into environments
that require approval, approvals will be successfully generated only if you
RLC - Approvers
role. If deployment dates are required,
specify them in the environment schedule, see
Scheduling into Environments
environments with approvals, the Start Deploy button is displayed only if
deployment dates are specified (even if they are not required in a rule).
After you click
Start Deploy, validation automatically
begins. If the deployment tasks are valid, deployment starts immediately.
However, if any task is invalid, deployment will not start. The release package
will remain in the Ready to Deploy state and the following message will appear:
"The current or locked environment has invalid tasks. See the
System Log for more information."
Check the deployment status.
After the deployment has been verified, click
Deployment Verified and enter any comments
needed in the
Message Log field.
After testing is complete, click
Complete Testing or
Failed Testing and fill out the resulting form
Labels and options on the page typically direct you on what to do
as you navigate through the deployment.
Important: You cannot add environments or change the options
once the release package is started on the deployment path. To add environments
and change the options, you must change the deployment path and start again.
Copyright © 2012–2018 Serena Software, Inc., a Micro Focus company. All rights reserved.