Working with Release Packages
A Release Package contains information about all the CIs (for example, documentation, test plans, services, and so on) associated with a Change and links to the Release that is deploying the Change.
Typically, the Change Manager might have already linked to a Release, or created a Request for Release.
In the following illustration, the Change record is linked to a standalone Release, which contains all the CIs associated with the Change. The Release is, in turn, linked to a Release Package which inherits all the CIs that are included in the Change.
Relationship between Change, Release, and Release Package for a standalone Release
The Release Manger can decide to stagger the Change between multiple Releases (for example, Master and Phase Releases) by creating multiple Release Packages for a single Change. For example, a Change that involves a major software upgrade can be staggered among Master and Phase Releases, each consisting of a Release Package that contains the CIs and Services that are affected at each phase of the Release.
|
Depending on the type of Change and its scope, a Release might or might not have a Release Package. A single Change record can have one or more Release Packages indirectly associated with it from the Releases. For example, if the Change involves updating a specific software on all the employees machines, the Change might be rolled out in phases by location or by organization. In such an instance, Release Packages are created for each phase of the Release. |
In the following illustration, the Change record is linked to multiple Releases. Each Release is in turn linked to a different Release Package. The Release Manager links only those CIs to the Release record and Release Package that will be included in the actual Release.
Relationship between Change, Release, and Release Package for phased Releases
|
|
Depending on the type of Change and its scope, a Release might or might not have a Release Package. A single Change record can have one or more Releases associated with it. For example, if the Change involves updating a specific software on all the employees machines, you might want to roll out the Change in phases by location or by organization, you create Releases for each phase. |
Create a Release Package for a Release
When you are creating a Release Package from the Release, the Release ID is already linked to the Release Package.
| 1. | Log in as Release Manager and open the Release workspace, then open the Release record for which you want to create a Release Package. |
| 2. | From the Release Package tab, click New. The New Release Package window appears. |
| 3. | Enter information into the fields. |
--fields--
| Field | Description |
|---|---|
| Name | Enter a title for this Release Package. |
| Description | Enter details of the Release Package. |
| Status |
Choose a status.
|
| Team | Choose from the drop-down list. Denotes the team responsible for the package. |
| Owner | Choose from the drop-down list. Denotes the package owner. |
| Change |
Optional. Enter the Change record ID to be implemented and linked to this Release Package.
|
| Release | The Release ID is automatically entered. |
. Click to find the change record.| 4. | Click Save.
Click Save  from the toolbar.
|
Repeat to add other Release Packages to the Release.
Add CIs to a Release Package
After you create a Release Package for a Release and associate a Change to it, you link those Configuration Items (CIs) that are part of the Release Package to the Release Package record.
| 1. | Within the Service Desk Console, open the Release Package workspace. The list of release packages appears. |
| 2. | Open the Release Package you want. The Release Package form appears. |
| 3. | From the CI tab, click Link. |
| 4. | Select the appropriate CI record and click Select. |
| 5. | Repeat to add CI records to the Release Package. |
| 6. | Click Save.
Click Save from the toolbar.
|