Associating releases with global configurations

Associate IBM Engineering Workflow Management (EWM) releases with global configurations by adding release links in the configurations.

Before you begin

To add or remove release links in global configurations:
  • You must be a member of the Global Configuration Management (GCM) project area that contains the global configuration that contains the target artifact versions.
  • For a shared global configuration, you must have the Configuration Lead role or higher, or Add or remove links privilege for the project or team area.

About this task

To enable linking of work items to specific versions of artifacts in other applications, you must associate a release with a global configuration, and the releases must be defined in the EWM application. For more information, see Enabling linking of work items to versioned artifacts.

By default, the release values of a global configuration are the same as the configuration from which it is derived, but you can set them explicitly. Baselines of a stream inherit the release values from that stream.

A personal stream inherits the release values from the underlying global stream, or can be linked to any release as set by the owner. If the release links of the underlying global stream are changed, owners must update the personal streams to match.

Configuration leads can take the following actions once or a few times during a release cycle to avoid inconsistencies in the future:
  • Create a new global stream, typically derived from a baseline of the previous release.
  • Remove any outdated release links from the newly created stream if the new stream is one of the following types:
    • A different variant, and must not be associated with the same old set of releases.
    • A stream for a new successor release. If the successor release has one or more predecessors in EWM, then the new stream is automatically associated with the predecessor releases. If not required, the predecessor releases can be removed from explicit association with the new stream.
  • Add the appropriate release links to the new stream.
Note: In complex scenarios, the release links can be automatically applied in bulk over many streams through scripting (REST and OSLC APIs).

To associate a global configuration with a release link, you must ensure that the Release link type is not removed from the Global Configuration artifact type in Manage Type Definitions. Otherwise, the Release link type is not shown in the Links tab of a global configuration. For more information, see Managing type definitions.

Procedure

  1. Open a component or configuration; then, click the Links tab and click Edit.
  2. Click Add Link and select the Release link type.
    A dialog box opens.
  3. Select one or more releases to add, and click OK.
    Note: All EWM project areas (that you are a member of) are available for selection. However, if you want to limit the list of available project areas, you must set the Project area associations are required for release links advanced property to true on the application's Advanced Properties page. Then, define project area associations (Uses – Configurations) from the GCM project area to each EWM project area. To know more about limiting project areas by enforcing project area associations, see Limiting release links by enforcing project area associations.
  4. Save your changes.

Results

The association is done. You can hover over a release link to find more details, such as project area, description, iteration, and predecessors.

Importing existing release links from EWM to GCM

GCM administrators can import preexisting associations from the EWM application to the GCM application to automatically associate release links to the global configurations.

Before you begin

You must have the Configuration Lead role or higher, or Add or remove links privilege for each global configuration type.

About this task

You can manually set up associations between releases and global configurations in the GCM application. New global configurations typically inherit the correct set of releases due to manual associations. But when you upgrade from a previous version, you must import the previous associations between releases and existing global configurations from the EWM application into the GCM application.
Example:
Image of a global configuration associated with a previous release

Suppose that a global configuration named Car 2026 was associated with Release 1.0 that was defined in EWM 7.0.1. You now want to import the existing association between Release 1.0 and Car 2026 in the 7.0.2 version. So, you can use the Import Release Links wizard in the GCM application to link Car 2026 to Release 1.0. Configuration leads can also find the related global configurations from the hierarchy of Car 2026 (such as Product Line 2026, Truck 2026, and Ignition 2026) to manually associate releases.

Procedure

  1. Open Administration Shows the Administration icon > Import Release Links.
    A window opens.
  2. Select the EWM project areas from where you want to import the release links. Click Select all to select all the project areas. Then, click Next.
    Note: All EWM project areas (that you are a member of) are available for selection. However, if you want to limit the list of available project areas, you must set the Project area associations are required for release links advanced property to true on the application's Advanced Properties page. Then, define project area associations (Uses – Configurations) from the GCM project area to each EWM project area. To know more about limiting project areas by enforcing project area associations, see Limiting release links by enforcing project area associations.
  3. Optional: Click Preview Import to preview the changes.
  4. Click Import Release Links to start the process.
    Review the changes that are applied after the import.
  5. Click Finish to exit.

Results

The bulk import process is completed.

Note: You can import the release links from the same project area again without any issues. The system takes care of all the associations in the background, and you can further check the association details in the preview section. Hence, you can safely select any project area when you do the bulk import.