Download 6.0.6.1 Release
April 23, 2019
Try
Buy

IBM Rational Team Concert

Task tracking Source control Agile planning

Rational Team Concert 4.0.6

Product Release / Trial | February 28, 2014
This is not the most recent version. We recommend Rational Team Concert 6.0.6.1 . This is made available for archival purposes and may contain bugs and/or security vulnerabilities. If you do download this version, it is being provided AS IS, without warranties of any kind, including the implied warranties of merchantability and fitness for a particular purpose. We strongly advise you review the support pages for this version and update the product or take actions recommended therein. Security bulletins contain instructions for the security vulnerability addressed therein, and may require upgrading to a newer version. Link to security vulnerability blog: IBM PSIRT blog.

Rational Team Concert 4.0.6 New & Noteworthy

Rational Team Concert 4.0.6 New & Noteworthy

Rational Team Concert is an integral part of the Rational solution for Collaborative Lifecycle Management (CLM). For new and noteworthy information about other parts of the Rational solution for CLM, see these pages:

New in previous versions of Rational Team Concert

For details about new features and functionality in previous releases, see these pages:

New in Rational Team Concert 4.0.6

Build

Hudson/Jenkins connection timeout property

The Hudson/Jenkins server integration supports a new property: com.ibm.rational.connector.hudson.connectionTimeout. If the Rational Team Concert server communicates with an unresponsive Hudson/Jenkins server, this property limits the amount of time spent waiting for a response.

Newly created Hudson/Jenkins build engines have the property added automatically to the properties on the Overview tab, with a default value of 30 seconds. Existing Hudson/Jenkins build engines default to a 30-second timeout unless the property is added to the Overview tab of the build engine. The unit of measurement is seconds and should be an integer value greater than 0. If the property is not present or is invalid, the default (30 seconds) is used.

If your Hudson/Jenkins server requires more than 30 seconds to respond to queries or requests, increase the property value on the corresponding build engine.

Build definition folders

When you have several build definitions, it can be difficult to find a specific build definition in the Eclipse Team Artifacts view. You can now organize the build definitions in a project area into folders. After you organize your build definitions into folders, other project area members can see the folder structure in the Team Artifacts view after they refresh the view.

Note: Build folders are only supported in the Eclipse client.

  • To use this feature, the "Manage Build Definition Folders" permission is required. Typically, this permission is given to roles that can save build definitions. The permission controls folder creation, modification, and deletion. You can set the permission in the team configuration of your project area.

    Manage build definition folder permission

  • To create a folder, right-click the Builds node or another folder, and then click New Folder. The project or team area of a folder determines who has permission to modify the folder and the Team Artifacts view can also filter based on it.

    Folder properties

  • You can move build definitions and folders to other folders by dragging them, or you can right-click the item and then click Move.

  • The build definition editor displays the containing folder structure.

    Build definition containg folder crumb

  • If you prefer to see all build definitions in a flat list as before, you can disable Show Folders from the Builds node in the Team Artifacts view or in the Eclipse preferences.

More control over the conditions that trigger the post-build deploy option

The following trigger options are now available:

  1. Enable or disable the entire post-build deploy.
  2. Set the trigger policy for the post-build deploy as one of the following choices:
    • Deploy always
    • Deploy if build has no errors (warnings allowed)
    • Deploy if build has no errors or warnings
  3. Abort the post-build deploy if there are incomplete build activities.
  4. Enable the post-build deploy option for personal builds.

trigger_policy.png

Rational Build Forge integration enhancements

You now have more control over which step logs are collected for a Rational Build Forge build. In the build definition, you can specify multiple individual steps or ranges of steps.

Build Forge step range configuration

You can also set the connection timeout with a property on the Rational Build Forge build engine. The default is 30 seconds.

Build Forge connection timeout property

If a Build Forge build completes or is deleted without corresponding events being received by Rational Team Concert, the integration now detects this and updates the corresponding Rational Team Concert build. Previously, it remained in the "in progress" status indefinitely, which required the user to manually stop the build. The frequency of these checks is 20 minutes by default, but it can be adjusted in the administrator web UI under Advanced Properties > Rational Build Forge Services Layer > Build Forge Connector Event Poller Task Build Forge Timeout Check.

Rational Build Agent engine support for TLS v1.2

When you configure the Rational Build Agent engines to use secure connections, you can choose which secure protocol to use. The build engine must be configured to use the same secure protocol as the Rational Build Agent that it connects to. The secure protocols that are supported include TLS v1.2.

ClearCase Importer

The ClearCase Version Importer can import Rational ClearCase views as Rational Team Concert baselines

The ClearCase Version Importer now has an option to specify a list of Rational ClearCase views, which are imported as Rational Team Concert baselines. You can specify them with either the --viewTags option or the --viewTagsFile option:

> ccc export ccase -d <intermediate data directory>
-i <View-relative root path to export>
--viewTags <space-separated ClearCase view tags>
--viewTagsFile <path to a text file that contains view tags>
...

The command then exports the view configurations to the intermediate data directory. When you run the import command, the view configurations are migrated to baselines in Rational Team Concert source control.

You can use this option to import your label types by creating Rational ClearCase views, setting its config-spec, and listing them to the command. Or you can list Rational ClearCase views that are attached to UCM streams, and the latest contents of the stream are imported as Rational Team Concert baselines. The import command does not create workspaces or streams that correspond to Rational ClearCase views, but you can find baselines, which are named as Rational ClearCase view tags, in the Rational Team Concert component. You can right-click the Rational Team Concert component in the Eclipse client and select Show > Baselines. Then, in the History view, click Show All in Repository.

Note: The ClearCase Version Importer continues to import all versions of files even if they are not visible in the listed Rational ClearCase views (as long as the file is visible in one of the views).

Increased robustness of the ClearCase Version Importer

The ClearCase Version Importer command could fail in situations, such as a network glitch or a scheduled outage to apply a security patch. This type of failure might occur when you migrate a large volume of data that takes a significant amount of time (as long as a week). In the past, you had to restart the migration commands. In this release, the failures are mitigated by these two enhancements:

  • When a command fails, you can rerun the command after fixing the root cause. The command resumes the export or import operation from the previous execution. You do not have to run the command from scratch.

  • You can plan ahead to migrate data incrementally with a smaller amount. The export command now has the --prevDirs and --pcodeDirsFile options:
    > ccc export ccase -d <intermediate data directory>
    -i <View-relative root path to export>
    --prevDirs <space-separated previously exported data path>
    --prevDirsFile <path to a text file that contains previously exported data path>
    ...

    When you export a large amount of data, you can identify subdirectories under the root to export, and you can export and import them separately. At the end, you need to export and import the root, and then you can specify the --prevDirs option to exclude previously exported files from your current export.

    For example, when you export data at M:\aView\aVOB\aRoot, you can first export subdirectories:

    > ccc export ccase -d C:\data\sub1 -i M:\aView\aVOB\aRoot\sub1
    > ccc export ccase -d C:\data\sub2 -i M:\aView\aVOB\aRoot\sub2
    > ccc export ccase -d C:\data\sub3 -i M:\aView\aVOB\aRoot\sub3

    Finally, you can export the root:

    > ccc export ccase -d C:\data\aRoot -i M:\aView\aVOB\aRoot 
    --prevDirs C:\data\sub1 C:\data\sub2 C:\data\sub3

    Then, the export and import of the root is divided to four smaller operations, and all those commands finish in a reasonable time.

    You can also use the --prevDirs or --prevDirsFile options when you have additional check-in versions to migrate at the same root, or when you have additional ClearCase views to migrate.

    Note: When you run the import commands, they run in the same order as the export.

ClearQuest Importer

The ClearQuest Importer now updates relationship links

In the Rational Team Concert 4.0.4 release, the ClearQuest Importer was enhanced to update work items when running the importer multiple times. If there was a relationship link (for example, a parent-child, duplicate of, or duplicate by link), and this link was removed on the Rational ClearQuest side, the link would not be removed on the Rational Team Concert side in 4.0.4 when performing an update. This limitation was removed in this release.

Client for Microsoft Visual Studio IDE

Rational Team Concert supports Microsoft Visual Studio 2013

Rational Team Concert now supports Microsoft Visual Studio 2013. If you are using Microsoft Visual Studio 2013, you can install Rational Team Concert into Microsoft Visual Studio 2013 and use the Rational Team Concert from the IDE.

When Rational Team Concert is installed, the help is displayed as follows:

Visual Studio 2013

Connecting to JazzHub from the Rational Team Concert Client for Microsoft Visual Studio

You can now connect to JazzHub from the Rational Team Concert Client for Microsoft Visual Studio.

If you are not yet connected to a Rational Team Concert repository, a new link named Manage JazzHub Projects is displayed in the Team Artifacts Navigator. Additionally, a new Manage JazzHub Projects button is available on the toolbar for the Team Artifacts Navigator.

Manage JazzHub Projects

Click the link or toolbar button to start a wizard to connect to JazzHub projects.

Manage JazzHub Projects Wizard

If you are new to JazzHub, the wizard contains links such as Register at JazzHub and Learn more about JazzHub. If you click these links, the appropriate page on the JazzHub website opens. If you are already a registered user, you can enter your JazzHub credentials to get to your JazzHub projects.

After your credentials are validated, the Manage JazzHub Projects wizard displays a list of JazzHub projects that you own or are a member of. You can select one or more project areas to connect to. Click Explore projects at JazzHub to explore JazzHub projects on the JazzHub website.

My JazzHub Projects

After you select one or more project areas, they are displayed as connected project areas in the Team Artifacts Navigator.

Connected JazzHub Projects

Dependency build and promotion

"Show summary" option added to build subset editor

A new Show summary option was added to the build subset feature. If you select this new option when you add files to a build subset by using rules or work items, a new Add Files Summary window opens. The summary window lists the criteria that you used to select the files, the file names, and number of files that are added to the subset.

Add Files Summary Dialog

Promotion process generates new promotion report

The promotion process now automatically generates a promotion report. The promotion report is called promotionReport.xml and is available on the Downloads tab of the promotion build result or as a link on the External Links tab. This report includes links to any build maps that are promoted during the promotion build.

Suppress build map links option added to promotion definition

Previously, build map links were automatically published to the build result of promotion builds. You can turn off this feature by selecting the check box on the promotion definition, which improves processing speed. Existing promotion definitions continue to publish the links by default, but new definitions do not publish build map links unless you select the option.

Publish build map links

Create snapshot option added to promotion definition

The promotion definition includes a new option to create a snapshot of the target stream before source code is promoted to it. If you select the option, a snapshot is automatically created when you run the promotion.

Create a snapshot of the target stream

Link added for promotionInfo.xml

The promotionInfo.xml file is used as an input to the promotion process and contains data about the members that will be promoted. A link to this file was added to the External Links tab, which displays this file in a table.

Follow-up action to run a target build

A new follow-up action named Run Target Build was added for the Promote Work Items (server) operation. Although component promotion runs a target build after the promotion completes, work item promotion does not include this option. With this follow-up action, you can also run a target build for work item promotion. You can configure this follow-up action in the Process Configuration > Operation Behavior section of your project area.

Process configuration for requesting a target build

Include child work items when creating a build subset

You can now include child work items when you create a build subset. For the "Add Files using Work Items" option, in the "Select Work Items" window, select the Include children of selected work items check box. Any files that are related to the child work items of the selected work items are added to the build subset.

Include children of work items for subset

Improved Enterprise Extensions dependency preprocessing

Enhancements include continued performance improvements in Enterprise Extensions dependency builds preprocessing speeds. Depending on the scenario, improvements in dependency analysis ranged from 10 to 30 percent, although in most cases performance remained the same. Each environment and build configuration is different, so results might vary.

Deployment

New Ant task: RetrieveChildrenWorkItems

A new Apache Ant task was added to calculate the child work items for a given set of work items. Inputs and outputs can be either work item IDs or work item UUIDs. This task can be used with the requestPackagingBuildTask task, for example, to collect all work items that descend from a parent shipment work item, and package their build outputs. This task can also be used independently to recursively find child work items for given parent work items.

RetrieveChildrenWorkItems Task

Enterprise Extensions system definition editors

Support the allocation of a normal PDS in data set definitions

When you define a data set, you can select a Partitioned Data Set (PDS) type to be allocated. The default is the Library (PDSE), but the PDS restriction for new data sets being allocated is removed.

Specify more attributes for temporary data set

When you define a data set, you can specify other attributes for temporary data sets, such as record format, record length, and data set type (PDS or PDS/E).

Allow a disposition of MOD in translators

When you define a translator, you can specify a disposition of MOD in the data set properties for DDs that are allocated to temporary data sets.

ISPF client

Add or remove components in the ISPF client repository workspace

In the ISPF client, you can add, create, or remove components from a repository workspace on the Edit Repository Workspace panel. These actions are available on the Repository Workspace panel.

ISPF CLient Edit Repository Workspace

To display the available actions for a component, enter a forward slash (/) next to a component in the list and press Enter.

ISPF CLient Components List Actions

Change the flow target of the repository workspace in the ISPF

In the ISPF client, you can change the flow target for the workspace. On the Edit Repository Workspace panel, type a forward slash (/) next to the current flow target and press Enter.

ISPF CLient Edit Repository Workspace

ISPF CLient Change Flow Target

To display all the available actions on a flow target, type a forward slash (/) next to a flow in the list and press Enter.

ISPF CLient Flow Targets List Actions

To add a flow target in your repository workspace, you can type an "A" action code next to a flow in the list and press Enter.

ISPF CLient Add Flow Target

Jazz source control

Locating change sets

The feature to locate change sets has been enhanced as follows:

  • Baselines can now be added to the Locate Change Set editor as search targets. To add baselines, users can drag baseline nodes from the Pending Changes or History view into the Search Targets table of the editor, or they can use the Locate Change Sets context menu item on a selection of baselines.

  • The Locate Change Sets option is now available on the context menu for streams, repository workspaces, and snapshots, as well as baselines. The selected nodes are added as search targets in the Locate Change Sets editor.

  • Build results can be dragged into the Search Targets table in the Locate Change Sets editor to have their corresponding build snapshots added as a search target. This action enables users to answer questions such as Are my changes in the build yet? or When did my changes make it into the build? by selecting a range of builds.

Locate Change Sets

Command line: List change sets associated with a work item

The "list change sets" command is enhanced to list the change sets that are associated with a work item. Users can specify multiple work items and indicate whether to list the change sets that are associated with the child work items.

Usage: 
					
scm list changesets [-m/--maximum <arg>] [--suspendedby <arg>] [--creator
	<arg>] [--created-after <arg>] [--created-before <arg>]
	[-p/--path <arg>] [-n/--name <arg>] [-t/--type <arg>]
	[-w/--workspace <arg>] [-C/--component <arg>
	[-b/--baseline <arg>]] [-r/--repository-uri <arg>]
	[-u/--username <arg> -P/--password <arg> | --certificate
	<arg> -P/--password <arg> | --smartCard -u/--username
	<arg>] [-j/--json]
				   
scm list changesets -W/--workitems <arg ...> [--include-child-workitems]
	[-r/--repository-uri <arg>] [-u/--username <arg>
	-P/--password <arg> | --certificate <arg> -P/--password
	<arg> | --smartCard -u/--username <arg>] [-j/--json]				     

Command line: Check-in command

The check-in command is enhanced so that it can set the comment of the change set, mark the change set as complete, and associate a change set with a work item. This enhancement affects the new change sets, as well as the change set that was explicitly specified in the command.

Usage: 

scm checkin [-u/--username <arg> -P/--password <arg> | --certificate
	<arg> -P/--password <arg> | --smartCard -u/--username
	<arg>] [-j/--json] [-v/--verbose] [-d/--directory <arg>]
	[-N/--no-local-refresh] [--max-changes <arg>]
	[-C/--delim-consistent] [-n/--delim-none]
	[-D/--checkin-deleted] [-S/--skip-deleted] [--comment
	<arg>] [--complete] [--workitem <arg>] [-c/--change-set
	<arg>] 

Commands for the command-line interface are now improved:

Perform operations on multiple items

The following commands are enhanced so that you can perform operations on multiple items:

  • set changeset: Set the same comment on multiple change sets or mark multiple change sets as completed.
    Usage: 
    	
    scm set changeset ([--complete | --current] [--comment <arg>])
    	[-r/--repository-uri <arg>] [-u/--username <arg>
        -P/--password <arg> | --certificate <arg>
        -P/--password <arg> | --smartCard -u/--username
        <arg>] [-d/--directory <arg>] [-w/--workspace <arg>]
        <change set...>
    

  • get attributes and set attributes: Get or set attributes for more than one workspace or component.
    Usage:
    		
    scm get attributes -w/--workspace <arg ...> ([--name] [--description]
    	[--ownedby] [--visibility]) [-r/--repository-uri <arg>]
    	[-u/--username <arg> -P/--password <arg> | --certificate
    	<arg> -P/--password <arg> | --smartCard -u/--username
    	<arg>] [-j/--json]
    			
    scm get attributes -C/--component <arg ...> ([--name] [--description]
    	[--ownedby] [--visibility]) [-r/--repository-uri <arg>]
    	[-u/--username <arg> -P/--password <arg> | --certificate
    	<arg> -P/--password <arg> | --smartCard -u/--username
    	<arg>] [-j/--json]
    			
    scm set attributes -w/--workspace <arg ...> ([--name <arg>] [--description
    	<arg>] [--ownedby <arg>] [--visibility <arg>])
    	[--process-area <arg>] [-r/--repository-uri <arg>]
    	[-u/--username <arg> -P/--password <arg> | --certificate
    	<arg> -P/--password <arg> | --smartCard -u/--username
    	<arg>]
    			
    scm set attributes -C/--component <arg ...> ([--name <arg>] [--description
    	<arg>] [--ownedby <arg>] [--visibility <arg>])
    	[--teamarea-scope] [-r/--repository-uri <arg>]
    	[-u/--username <arg> -P/--password <arg> | --certificate
    	<arg> -P/--password <arg> | --smartCard -u/--username
    	<arg>]
    

  • scm daemon stop: This command is enhanced to take in multiple ports or multiple share roots. A new --all option is available for stopping all running SCM daemons in the system.

    Note: All three options are mutually exclusive.

    Usage: 
    	
    scm daemon stop (-a/--all | -p/--port <arg ...> | [share-root...])
    

Locate change sets in baselines

A new --baseline option is available for searching for change sets in baselines.

Usage: 
	
scm locate ([--projectarea <arg> | --teamarea <arg>] [-w/--workspaces
	<arg ...>] [-s/--snapshots <arg ...>] [-b/--baselines <arg
    ...>]) [-r/--repository-uri <arg>] [-u/--username <arg>
    -P/--password <arg> | --certificate <arg> -P/--password
    <arg> | --smartCard -u/--username <arg>] [-j/--json]
    [-v/--verbose] [--include-related] [[-C/--change-sets] |
    -W/--workitems [--include-child-workitems]] [--]
    <selectors...>

Associate a remote work item to a change set

The add work item command can now accept work items from a remote repository. You can specify the work item number, followed by the repository URI or nickname (@repoUri or @repoNickname).

Usage: 
	
scm add workitem [-r/--repository-uri <arg>] [-u/--username <arg>
	-P/--password <arg> | --certificate <arg>
    -P/--password <arg> | --smartCard -u/--username <arg>]
    [-w/--workspace <arg>] <change set> <work-item-number>
			
change set: The change set. To specify the change set, use its alias or UUID[@repo].
work-item-number: The ID[@repo] of the work item to associate with the change set.

Promotion

"Include impacted outputs" option added to work item promotion wizard

A new option, "Include impacted outputs," was added to the work item promotion feature. When you select the new option, the files that are affected by the work item promotion, but not directly included, are added to a list that you can select from.

Include impacted outputs option

When the list of affected files opens, you can select any of the files from the list to exclude them from the promotion.

Impacted files listing

The summary page then displays the outputs for the files that were not excluded.

Impacted outputs summary

Reporting

New Advanced release burnup report

Advanced Release Burnup report

New advanced team velocity report

Advanced Team Velocity report

New cumulative value flow by state report

Cumulative Value Flow by State report

Tracking and planning

Plan editor support for deliverable attributes

This release adds support in the plan editor to display and edit attributes of type "deliverable." This includes the built-in Found In attribute, as well as custom attributes of this type. Deliverable attributes can now be mapped as planning attributes in the project area process and can be selected as supported columns in the plan editor.

Found In column in a plan

Work Item Activity widget

The Work Item Activity widget is available in the Work Item widget catalog. You can watch changes to one or more projects as an activity stream, and you can configure the widget to show activities based on your level of interest (contributor or follower). You can choose not to group the activities, or you can group them by time or priority:

  • None: A single stream of activities, with the most recent activity on top.
  • Time (with three sections):
    1. Today: Activities that occurred today.
    2. Earlier this week: Activities that occurred this week before today.
    3. Last two months: Activities that occurred in the last two months before this week. Older activities are not shown.
  • Priority (with three sections):
    1. My Events: Messages and requests for me, and changes to the work items that I own (for contributor roles).
    2. My Subscriptions: Only activities with changes to the summary, description, comments, and state in work items that I am subscribed to.
    3. Project Activity: Work items resolved as fixed, pand new work items (for contributor roles).

Activities grouped by priority

Drag items between plans

In the web client, you can drag work items between plans by opening plans in separate browser windows, and then dragging items between the windows.

In plans, you can now create work items of various link types by using the context menu.

Delete draft items

In the web client, you can delete a draft item in a plan by hovering the mouse pointer over the actions column of the work item, and then clicking Delete Draft Item.

Refresh work items in a plan

You can refresh one or more work items in a plan from the Actions column. Select one or more work items to refresh, click the down arrow of one of the work items, and then click Refresh Work Item.

Keyboard shortcut to refresh plans

To refresh a plan, in a plan view, use the shortcut Ctrl-Shift-R.

Sort order change of iterations when browsing plans

To make it easier to find the most relevant plans, the All Plans, Current Plans, and My Current Plans pages now display iterations from newest to oldest.

Work items using deprecated presentations must be reconfigured

In Rational Team Concert 4.0, some work item presentations were removed because there were more appropriate or equivalent presentations available. An example is displaying an HTML attribute as text or a string as a selection list. When the presentations were removed in 4.0, they could no longer be added to customized work items. Existing work items that were configured to use them continued to work. In Rational Team Concert 4.0.6, a warning is displayed that the presentation is deprecated. This warning is in preparation for removing the presentations entirely in a future release. Work items that use these deprecated presentations must be reconfigured to use supported presentations. The following table includes a complete list of deprecated presentations:

Attribute type Deprecated presentation
Medium HTML String
Large HTML String
Medium HTML Text
Large HTML Text
Small String HTML
Medium String HTML
Large String HTML
Small String Description
Medium String Description
Large String Description
Small String Multi-Select List
Medium String Multi-Select List
Large String Multi-Select List
Small String Checkbox Multi-Select List
Medium String Checkbox Multi-Select List
Large String Checkbox Multi-Select List