The Release Package process app includes two applications: Release
Package and Deployment Path. Each has a single workflow.
- Release Managers
- Package Creators
- Release Engineers
Release Packages follow a process organized into these stages:
The first stage of the Release Package is the definition stage.
While the release package is in the Define stage, release engineers
- Select release type, which limits the deployment paths available
for the release package.
- Add deployment tasks. These can be newly-created tasks specific to
the release package or tasks copied from task templates and other release
packages. Deployment tasks can be added, reordered, or deleted as needed as the
release package is deployed through the deployment path.
- View and associate requests and deployment units.
Once accepted, the release package moves to the
In the Deliver stage, the release packages are deployed.
- Accepted release packages move to the
Ready to Deploy state.
- Once the deployment is started, deployment tasks initiate the
related deployment processes and deploy any deployment units.
- Once all deployment tasks are complete, the release package moves
Deployed state. If any deployment tasks fail, the release
package is sent to the
Deployment Error state. Failed release packages can be retried
or returned to development for more work.
- Successful deployments move to the Verification stage.
- If failure tasks exist or are required, upon Fail Deployment the
release package goes to the Failure stage of the workflow.
In the Failure stage, any failure tasks are run in the deployment path
environments associated with the train.
- The release package is deployed to the first eligible environment
in the deployment path.
- The failure tasks associated with the release package and with its
child release packages are executed in the environments.
- After all failure tasks are completed, the release package goes
into the To Construction state on the environment specified as the "fail to"
In the Verification stage, the functionality implemented by the
release packages is verified.
Copyright © 2012–2017 Serena Software, Inc. All rights reserved.