After you have linked child release packages to their parents, you can
work with the child packages.
A child release package:
- Cannot have any child release packages
- Has its own deployment task collection
- Follows the parent's workflow; deployment must be done at the parent
level
- Follows the parent's deployment path
- When added to the parent, causes the parent to be reset to the
beginning of the deployment path
- Retains a history of previous deployment paths it had before being
added to a parent
- Retains a history of new deployment paths started after having been
added to a parent
After a child is added, the child release packages have a
Parent Package Details tab instead of a
Deployment Path tab, to indicate that the
deployment path is now following the parent release package path.
The parent release package has an additional tab called
Child Packages that lists the child packages. In
this list, you can do the following:
- Click the child release package link to go to the item.
- Click the eye icon to see a quick view of the child release package
information in a pop-up.
- Through the
Actions menu beside each child release package,
you can select the following options:
- Edit Deployment Tasks
- Edit Deployment Units
- Unlink Child Package
- Edit Requests
- Reload Deployment Unit Data
- Reload Request Data
Copyright © 2012–2016 Serena Software, Inc. All rights reserved.