You should create a release package when you are ready to begin
configuring the deployment details for a release. You can create release
packages by submitting to the release packages project. If using release
trains, you can create a release package directly from a release train.
By default release packages are standalone, but they can be designated
as parent or child packages. See
Designating Release Packages as Parents
Linking Release Packages.
- Ensure you have set up the minimum objects required before you try to
create a release train.
Creating Release Elements.
- You must have at least one active deployment path.
To create a release package:
- Depending on whether you are using release trains, open the release
packages project submit form in one of the following ways:
select a release train, and in its
Overview tab, click
Create Release Package.
+New and select your release packages
(By default, the Release Packages project is used to store
- Fill out the required fields.
Tip: Include the version of the release package in the
Description so that you can later report on
and compare release package versions through standard
- Fill out optional fields as needed.
- Use task templates to save time and enable reuse of deployment
tasks. In the
Overview section, in the
Use Task Template field, select a task
template from which to copy deployment tasks.
- Select custom column items for add and display of deployment
units and requests. See
- Select whether to require that failure tasks be run if the
deployment fails in an environment. See
Adding Failure Tasks.
- Select plugin configuration fields for which the values can
be overridden for this release package. See "Overriding Configuration Settings"
in the plugins documentation.
- Select task action rules to restrict the set of rules that
apply for this release package. If none are selected, all defined task action
rules apply. See "Task Action Rules" in the plugins documentation.
- Select whether or not to bypass the
Deployed state. By default, the release package process
flow bypasses this state. If you want to have users manually transition to this
state, you can set the option to No.
This places the release package in the
Note: You can instead click
Save as Draft, which places the release
package in the
Construction state, where it must be configured before
delivering it to the release engineering team for acceptance.
- Configure and manage the release package using the tabs that appear
in the form.
The required fields when you create a release package are as follows:
The tabs available from a release package once it is created are as
- Deployment Path: View the deployment path for this release
package, including detailed deployment history for each environment in the
- Deployment Units: View deployment units for this release
Adding Deployment Units.
- Deployment Tasks: View and add deployment tasks and failure
tasks and view deployment executions for this release package. See
Adding Deployment Tasks.
- Requests: Select requests to associate with this release
- Approvals: Select approvals to associate with this release
package. Auto-generated approvals appear here when a release package is
deployed to an environment that requires approval.
- Notes/Attachments: View notes and attachments that have been
added to the item through the
More option and related email correspondence.
- History: View the history of the release package item. This
System information, such as currently set task
Updating Release Packages
Once created, you can update release packages as follows:
- In the
application group left navigation, expand the
Release Packages section and select one of the
activities sections to display the desired list of release packages.
- Select a release package and click the
Update button to edit it.
Options available depend on the process app workflow. For details on
the default workflow, see
About the Release Train Process App.
Copyright © 2012–2019 Micro Focus or one of its affiliates. All rights reserved.