Creating releases and specifying release details
To create a release, configure the lifecycle for the release, select the applications that are part of the release, and create approvals for the release's phases.
- Create or import applications for the release. See Managing applications with the Applications page.
- Ensure that the team assigned to the release has the applications you intend to use assigned to it. See, Assigning applications to teams.
- Create a lifecycle for the release. See Creating lifecycles.
- Configure the release environments for the release. Ensure that the application you intend to use are assigned to the release environments. See Configuring release environments.
- Create a notification scheme. The notification scheme defines the notification rules for the release or, if you attach a scheme to a phase, for individual phases. For more information, see Configuring notifications.
- If you want to use notifications, make sure that an SMTP server is configured.
- To map events to releases, enable the feature flag in the
installed.propertiesfile as follows:
installed.propertiesfile is located in the installation_directory/conf/server/ folder. After you modify the
installed.propertiesfile, restart the server.
In outline, you create a release by selecting a lifecycle, team, and target date. Before you can run deployments with the new release, you must assign release environments to the lifecycle's phases. After a phase has at least one release environment assigned to it, you can run deployments for the phase. In most cases, you assign applications to the release, although it is not required.
You can customize a release at any time. You can change the deployment plans, add phase approvals, notification schemes, and process checklists. You can also add events to a release. If you add enterprise events, the release can participate in enterprise-wide release events.
- From the IBM UrbanCode Release dashboard, click Releases & Deployments.
On the Releases page, click Add New, and then
provide these details:
Specify a name for the release.
Use a name that is meaningful to your organization and its release processes. If you schedule releases based on sprints or product iterations, include that information in the release name.
In the Lifecycle field, select the lifecycle for the release.
The lifecycle determines the number and order of phases in the release. Typically, to complete a release, you run a deployment for each phase in the lifeycle. You can change the lifecycle for the release later, if necessary.
In the Team field, select the team for the release.
If you assign a team to a release, only members of that team can interact with the release. See Security teams.
- In the Target Date field, specify the planned completion date for the last phase of the release.
In the Description field, specify a description
for the release.
Provide details about the release that other members of your enterprise find meaningful or that uniquely identify the release.
In the Notification Scheme list, select a
The notification scheme defines the notification rules for the release. The scheme's rules are used for all notification events. You can override the scheme by attaching a scheme to a phase, or to a deployment when you schedule a deployment. If you attach a scheme to a phase, the rules in the phase's scheme are used except for the release-related events, which continue to use the rules in the release's scheme. For information about notifications, see Configuring notifications.
The new release is displayed in the list of releases.
- Specify a name for the release.
To specify applications that are included in the release, complete these steps:
On the Releases tab, click the name of the release.
The Release Detail page is displayed.
- Next to Participating Applications, click Add New.
- In the Application list, select an application, and then click Save.
- Repeat steps a and b to add all applications that are part of the release.
To limit the application versions included in the Enterprise View and
Applications and Versions pages, click the Update Filter
link for an application. Enter text used to be used as a filter. You can use the asterisk character
(*) as a wildcard in your filter text.
The filter affects the application versions available in several pages.
- Only information for application versions that match the filter is displayed in the Enterprise View page.
- In the Applications and Versions, only application versions that match the filter are available to use in a deployment. Use the filter to ensure that only versions ready for deployment are available.
- On the Releases tab, click the name of the release.
To add release environments to a phase, complete these steps:
To run a deployment for a phase, at least one environment must be assigned to the phase. You can run deployments in the assigned environment any time during the period that is defined by the start and end dates. For more information, see Reserving release environments.
- Under the Release Pipeline section, for a phase click to open the New Environment Reservation dialog.
Specify the start date and end date during which the release environment is reserved for the
The environment is reserved for the selected phase during the specified time.
In the table of environments, select one or more environments, and then click
You can filter the list to show only those environments that are available for the selected dates by enabling the Show only Environments without conflicts field.
- Repeat steps a to c to add release environments to each phase of the release lifecycle.
To set a default start time for release environments, click the Edit
Phase icon , and in the Start Date field, specify the date.
Release environments that are associated with the phase are reserved beginning on the specified date. You can override the default setting.
To define approvals for a phase, complete these steps:
If a phase has an approval that is defined for it, deployments for the phase cannot start until a user with the expected role approves it.
- In the Release Detail tab, in the row for the phase, click the Edit Phase icon.
- Next to Phase Approvals, click Add New.
- Specify the approval name, and, from the Role list, select the role that a user must be assigned to complete the approval.
- Click Save.
- Repeat steps a to d to add additional approvals.
In the row for the phase, click the Edit Phase icon, and then use one of
these methods to change the deployment plan for a phase:
By default, the deployment plan is inherited from the lifecycle that is selected for the release. The deployment plan for the default lifecycle is the Default Plan. You can change the deployment plan for any phase in the release.
- To select a deployment plan from the current release, from the Default Plan list, select the deployment plan, and click Save.
- To copy a plan from another release, from the Default Plan list, select Create/Import Plan. Using the Create a New Deployment Plan dialog box, click Copy from a plan, and specify a name for the new plan. Finally, from the Copy From list, select the plan, and click Save. To start with a fresh, blank deployment plan, select None (Empty Plan).
- To copy a plan from a CSV file, from the Default Plan list, select Create/Import Plan. Using the Create a New Deployment Plan dialog box, click Import from CSV, and specify a name for the new plan. Finally, browse to the file location and click Save. A new deployment plan is created by using the values in the CSV file. For information about exporting deployment plans, see Exporting deployment plans to CSV file.
To add a notification scheme to a phase, complete these steps:
You can override the scheme that is attached to a release by adding a scheme to a phase. For example, you might want to use a different scheme for your productions phase. If you do not attach a scheme to a phase, the scheme that is attached to the release is used instead.
- In the Release Detail tab, in the row for the phase, click the Edit Phase icon.
- In the Notification Scheme, select a scheme.
Add a process checklist by using one of these methods:
- To add an item to the checklist, next to Process Checklist, click Add New, and enter the details. Repeat this step for all release processes.
- To import a process checklist from a template, click Import from Template, select the template from the Process Checklist Template list, and click Save. See Creating process checklist templates.
To add events to the release, complete these steps:
- Under Events, click Add New.
- In the Name field, type a name for the event.
From the Type list, select the event type.
If the type is of the Related Deployment Module category, the release can participate in release events with other releases. For information about event types, see Creating event types.
Specify a start date for the event, and an optional end date.
The calendar widget displays other events that are scheduled for selected dates.
In the Releases list, select the releases to which to add the
By default, the current release is selected, but you can clear it. If you select more releases, the event is added to each of the selected releases.
If you did not select any release for the event, the event is still saved and is available for use later.
- To track details of associated work, assign changes to a release. See Creating and organizing changes.
- You can see information about the status of a release, and the applications that are associated with it in the Enterprise view. See Monitoring releases with Enterprise View.
- You can schedule deployments for that release. See Deploying.
- You can review the progress of the release in the Pipeline view. See Managing pipelines with the Pipeline view.
- Review release changes on the Change History page. You can filter the information by activity type, such as deletes or edits.