This section describes a typical successful flow using planning release
The steps in this section assume that
has been installed and configured, and that release elements have been created
using the steps in
Creating Release Elements.
Note: The flow you use in your implementation may be different.
- Create standalone release packages.
- Add requests, deployment units, and deployment tasks to the release
- Deploy, approve, and validate release packages through the test
environments in the deployment path.
- Deliver production-ready release packages to the release engineering
team for acceptance.
- Optionally organize the release packages in a logical parent-child
hierarchy for attachment to a release train.
Tip: This is typically done in preparation for deploying
the release train, and is therefore done after candidate release packages have
been tested through test environments. Once the release packages are ready to
be released as part of a particular release train, the release package
hierarchy can be added to the release train.
- Create a planning release train and add exit criteria and milestones.
- Add all standalone and parent release packages targeted for this
release to the release train.
Tip: The linked release packages will be changed to follow
the production deployment path associated with the release train.
- Verify and send the release train for release approval.
- Deploy and approve the train's release packages through the
production deployment path.
Important: Planning release trains track the flow of the
release, but do not actually drive the deployment; that is done only through
release packages in this scenario. If you want release trains to drive
deployment, use deployable release trains instead.
Copyright © 2012–2017 Serena Software, Inc., a Micro Focus company. All rights reserved.