Deployment initiates the deployment tasks that you have configured and
You must have completed the release package configuration, including
adding the deployment tasks.
It is recommended that you validate the deployment tasks before
beginning the deployment. See
Validating Deployment Tasks.
Starting the Deployment
To run a release package deployment:
- Select the release package you want to deploy.
Note: Standalone and parent release packages can be deployed
directly. Child packages are deployed when their parent release package is
- Move the release package 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 the deployment tasks associated
with the release packages begin. The deployment executes each of the deployment
tasks in the order specified.
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. Refer to
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
Note: Even if you have a schedule and the start date has not yet
arrived, when you click
Start Deploy, the deployment starts; the
schedule is not enforced by the software, and is for informational purposes.
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.
Checking Deployment Status
To check the status of the deployment:
- Select the release package's
Deployment Tasks tab.
- Filter the list of deployment tasks by
- Refresh the status as needed using the refresh button.
If the deployment fails, investigate and fix whatever caused the
problem, such as the configuration in the integrating product, a selection or
sequencing problem in the deployment tasks, or configuration in the target
environment itself. If the environment allows redeployment, you can redeploy
the release package to the same environment. If it doesn't allow redeployment,
you must return the release package to construction and progress the release
package back through the process from there.
Deploying to the Next Environment
Use the provided options to transition the release package through the
- When the deployment is marked complete for an environment, a list
appears with the available environments for the next deployment.
- You will see the upcoming optional and required environments
listed, and you can select the one to which you want to deploy, skipping the
optional ones if desired.
- Start the deployment in the next environment and continue until you
have completed the deployment to the last environment in the deployment path.
- When the deployment is completed in the last environment of the
deployment path, a message appears telling you that the release package has
been promoted to all environments and the release package is now complete.
Viewing Deployment Executions for the Path
View information about deployment executions in the
Deployment Path tab.
Select deployment executions to see information for each deployment
- The path shows only the latest deployment into an environment, so
when there are retries and redeploys, the prior ones are not shown.
- Click the information icon in an environment box to see the list of
deployment units deployed to that environment. This information is also only
for the latest deployment into that environment.
If you do not see the complete report below the
deployment path and the environments to which you have deployed are not shown
in color, refer to
Troubleshooting the Deployment Path.
Copyright © 2012–2016 Serena Software, Inc. All rights reserved.