IBM Rational Team Concert
Task tracking · Source control · Agile planning
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 5.0 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 CLM applications, see these pages:
New in previous versions of Rational Team Concert
For details about new features and functionality in the previous release, see Rational Team Concert New & Noteworthy 4.0.6.
New in Rational Team Concert 5.0
- Build
- ClearCase Importer
- ClearQuest Synchronizer
- Context-aware search
- Dependency build and promotion
- New Enterprise Extensions option to view build maps
- New Enterprise Extensions option to view system definitions history
- New option to rebuild outgoing change sets in personal builds
- RPG language enhancements to support free-form statements
- OpenSSL Rational Build Forge Agent removed from z/OS build system toolkit
- Enterprise REST Gateway removed from z/OS build system toolkit
- Deprecated dependency builds no longer supported for z/OS
- Additional load options for the IBM i dependency build
- Log loading during a dependency build
- Buildable subset APIs
- Source code data scanner now checks for file encoding
- Deployment
- Enterprise Extensions
- Full-text indexing
- ISPF client
- Jazz source control
- Fill-the-gap feature
- Duplicate a stream or workspace (command-line interface)
- Auto-merge during resume and resolve operation (command-line interface)
- Highlight common ancestor for conflicts (Eclipse client)
- Required migration of existing databases
- Version ID feature
- Accept and deliver work items
- Support for configuring external compare tools
- Customizing the behavior of Jazz source control operations from the browser
- Rational Team Concert Git integration
- Rational Team Concert reports
- Tracking and planning
Build
New file permission setting for the Build Agent
The new default permission setting for files transferred to the Rational Build Agent is 775.
The format of this setting is the octal representation of chmod permissions:
- Owner: Read, write, and execute
- Group: Read, write, and execute
- All: Read and execute
You can override the permission setting by configuring the Default File Permission property on the server properties administration page, under the "Build Agent" section. If the property is empty, the default permissions are inherited from the build agent user that runs the build.
teamFetch Ant task supports load rules
The teamFetch Ant task now supports the specification of load rules. Load rules can help configure which items to load
and where to load them. Load rules work in conjunction with the other arguments that configure the fetch operation (for example, the components to exclude and whether a root folder is created for a component). If a component in the workspace to load has a load rule that defines what to load from it,
the load rule directs what to fetch. Otherwise, the entire content of the component is fetched (if it isn't excluded). Load rules can be identified by
either UUID or by repository path.
View build definition folders in the web client and the Rational Team Concert client for Microsoft Visual Studio
Build definitions are now organized in the web client by the folders that were created in the Eclipse client.
In addition, if build definitions are organized under a shared hierarchy of folders in the Eclipse client, you can now view them in the Rational Team Concert client for Microsoft Visual Studio. You can also move build definitions and build definition folders between existing folders.
Prebuild checks for SCM changes
For Rational Build Forge builds, the integration now checks scheduled builds for SCM changes before starting the build in Rational Build Forge. If there are no SCM changes to build, no Build Forge build is created, and the pending Rational Team Concert build is deleted. This process applies to scheduled builds only, and the build definition's SCM configuration option for Build only if there are changes accepted must be selected. You can disable this behavior by adding a build property to the build engine with the name buildforge.preBuildScmCheck and a value of false.
ClearCase Importer
Performance improvement of the ClearCase Version Importer
The ClearCase Version Importer is enhanced to run faster. The importer now issues fewer cleartool commands for the export operation, and the source control operations of Rational Team Concert can handle a large volume of data, which results in better performance. The following scenarios are improved:
- The export of multiple-view configurations is faster. The export of five configurations completed 1.4 times faster than in the 4.0.6 release.
- The directory look-up of the export is faster. You can see the improvement with Rational ClearCase data that has a large number of files, but not many versions for each file. The performance is 1.8 times faster than in the 4.0.6 release.
- The version attributes are retrieved faster in the export command. The export of about 10,000 versions was more than 4 times faster than in the 4.0.6 release.
- The restart of the export command resumes the export operation 3 times faster than in the 4.0.6 release. The incremental export option is also faster.
- The import of multiple-view configurations is faster. The baseline creation completes more than 110 times faster than in the 4.0.6 release when importing about 200,000 versions. The total performance of 9 configuration import is 35 times faster.
- The import of large-scale data is faster. The test with about 100,000 files shows more than 5 times improvement of the import operation.
Note: The improvement results are reference data and depend on your Rational ClearCase and Rational Team Concert configurations, as well as the amount of the data.
Selective version import of the ClearCase Version Importer
Rational ClearCase versions can be selectively migrated by specifying filtering options, such as ignoring obsolete branches or ignoring versions that are older than a specific date. Five new options were added to the export command:
- --noHistory: Exports versions selected by views without predecessors.
- --noMergePredecessors: Exports versions selected by views and their direct predecessors.
- --onlyPredecessors: Exports versions selected by views and their merge predecessors.
- --noObsoleteBranches: Exports versions only from non-obsolete branches and non-obsolete branch types.
- --since date and time: Exports versions created since a specific date and time, expressed in an ISO 8601 format, such as "1994-07-03T00:00:00Z" for 3 July 1994.
You can select one of the options and migrate versions to Rational Team Concert source control selectively. For sample option results, see Filtering for the ClearCase Version Importer.
New command to import change set links from Rational ClearQuest and Rational ClearCase UCM integration
A new command was added to the ClearCase Version Importer so that you can migrate change-set links from Rational ClearQuest and Rational ClearCase UCM integration to Rational Team Concert. When the Rational ClearQuest records are imported by the ClearQuest Importer and the Rational ClearCase versions are imported by the ClearCase Version Importer, you can migrate the change-set links by using this new command:
> ccc import ucmLinks -r [your RTC repository URL]
-u [your RTC user ID]
-P [your RTC user password]
-d [ClearCase Version Importer data]
--project-area [RTC project area name or UUID to lookup work items in]
The change sets and work items are linked as in the following example:
For more information, see Migration of the ClearQuest-enabled UCM by the ClearQuest Importer and the ClearCase Version Importer.
ClearQuest Synchronizer
New option to add a ClearQuest Bridge link for synchronized items
You can now configure the ClearQuest Synchronizer to automatically create a ClearQuest Bridge link between a synchronized work item and a Rational ClearQuest record. Users of the ClearQuest Synchronizer often want to synchronize more fields, but it costs administrators more to keep the synchronization running. Creating a ClearQuest Bridge link enables users to more easily navigate synchronized records, and enables administrators to synchronize fewer fields and reduce the total cost of ownership. This link can also be configured for the ClearQuest Bridge user to automate the item and link creations across systems.
The resulting work item has links such as in this image:
First, you must configure both the ClearQuest Synchronizer and the ClearQuest Bridge. Then, you can enable the feature by editing the cqconnector.properties file of the ClearQuest gateway. For more information, see Configuring the ClearQuest Synchronizer to create OSLC links.
Context-aware search
New Select All option for the context-aware search
The context-aware search user interface now includes an easier way to select all components for a project area or stream. Previously, if you wanted to search all components, you had to select each component individually. Now a Select All button is available with the Select Loaded and Deselect All options. The button is added to Component Selection window.
Dependency build and promotion
New Enterprise Extensions option to view build maps
An option to view the build map of a buildable file is available from the context menu for a local file that has been shared, a remote file, or from the Source Code Data result view.
New Enterprise Extensions option to view system definitions history
A History tab is now part of the Enterprise Extensions system definitions. On the tab, you can see all changes to a system definition. Similar to the work item history, you can see the changes made over time by different users to the system definitions. From the History tab, you can review the state of the system definition at any time, which is useful for debugging and fixing dependency build problems. In this release, the full history is available only for z/OS translators, and the basic history is available for the other system definitions. The full history for the other system definitions is being developed.
New option to rebuild outgoing change sets in personal builds
By default, personal builds compare your personal sandbox workspace with the latest successful team build snapshot and rebuild all incoming and outgoing change sets. A new option allows you to limit personal builds, so that only your outgoing change sets are built. The option is available from the Jazz Team Server administration page under Configuration > Advanced Properties.
RPG language enhancements to support free-form statements
The ILE RPG scanner is updated to recognize the latest changes to the RPG language, which expands free-form statements beyond C-specs into F, D, H, P specs. See this article for more information on these RPG language changes. The ILE RPG scanner can now detect dependencies from free-form declarative statements, such as dcl-f and dcl-ds. The IBM i dependency builds detect these changes and rebuild RPG programs when these dependencies change.
OpenSSL Rational Build Forge Agent removed from z/OS build system toolkit
The Rational Build Forge Agent version that uses OpenSSL is removed from the build system toolkit for z/OS. Use the z/OS System SSL version of the Rational Build Forge Agent.
Enterprise REST Gateway removed from z/OS build system toolkit
The Enterprise REST Gateway has been deprecated for several releases. The gateway is removed from the build system toolkit in Rational Team Concert 5.0. Instead, use cURL, a command-line interface for sending and receiving files using a URL syntax.
Deprecated dependency builds no longer supported for z/OS
The deprecated build template named Dependency Build - Rational Build Agent is no longer supported, and builds that are defined with this template must be migrated to the z/OS Dependency Build - Rational Build Agent template. The New Build Definition wizard does not list the old template as an option, and build definitions that use the old template fail. You can begin the migration process by clicking the error message in the build definition.
Additional load options for the IBM i dependency build
The IBM i dependency build and the z/OS dependency build now have synchronized features for load options. The IBM i dependency build can now load all the changes in the workspace to the resource with the resource prefix at the beginning of the build. The build can also load to the IFS at the beginning of the build. The build has support for creating folders for components, excluding components from being loaded, and following a load rules file for what to load.
Log loading during a dependency build
In previous releases, during a dependency build, you could not see what was being loaded and which commands were being run to perform the load. In the build definition for the dependency build, on the Jazz Source Control tab, in the Load Options section, there is an option for Log Loading. When you turn on this option, a new log file is produced and is attached to the build results. This file shows which commands ran to perform the loading.
Buildable subset APIs
Several service and client APIs were added so that buildable subsets can be created from work items or a list of files.
The buildable subset APIs are available from the following interfaces:
- com.ibm.team.enterprise.buildablesubset.common.IBuildableSubsetServiceAPI
- com.ibm.team.enterprise.buildablesubset.client.IBuildableSubsetClientAPI
Source code data scanner now checks for file encoding
In prior releases, Enterprise Extensions source code data was collected by using the default file encoding in the server JVM, not the encoding that is specified for the file. Scanners now check the Character Encoding attribute that is specified for each file in source control. If no encoding is specified, or if the specified encoding is not valid, the file is processed with the default file encoding in the server JVM. This source code data collection change happens automatically, so no configuration changes are required.
Deployment
IBM i data migration options
Several options for the IBM i deployment feature were added to improve deployment for database files.
The following improvements are included:
- The ability to copy existing data from physical files while new copies are being deployed
- An option to call a user-defined command to deploy each physical file (if any files require specific handling during deployment)
- An option to omit saving all physical files to the rollback archive (for teams that prefer to back up database files independently instead of using the deployment process)
Enterprise Extensions
Control permissions for generated z/OS logs
You can now modify the file permissions of files that are generated by z/OS UNIX System Services (USS) during Enterprise Extensions operations.
Enterprise Extensions installation verification process
To improve the installation experience, a new installation verification process was added for the following Enterprise Extension features:
- ISPF client
- ISPF gateway
- Rational Build Agent
The installation verification process is started from a JCL sample, which enables the administrator to select the verification processes to run.
Enterprise Extensions performance improvements
Enterprise Extensions features are enhanced, resulting in performance improvements. These results are from internal performance testing. Each environment and build configuration is different, so the results might vary.
- Dependency build improvements: In performance testing for typical dependency builds in Rational Team Concert 5.0, there were improvements of nearly 15 percent when compared to the Rational Team Concert 4.0.6 test environments. Performance gains are a result of improvements in the collection of buildable files and processing compilation results. In some test cases, the buildable file collection improved by as much as 60 percent, and the processing compilation results improved by approximately 10 percent.
- Promotion improvements: Overall promotion performance improved up to 40 percent when compared to the Rational Team Concert 4.0.6 results. The greatest gains are primarily from improvements in finalizing build maps, which improved up to 70 percent in some tests.
- Improvements in source code data collection and queries: Source code data collection improved by up to 35 percent compared to the Rational Team Concert 4.0.6 results. Client-side processing of source code data queries improved by as much as 80 percent for large result sets.
Full-text indexing
Unique names for full-text index directories
Before the 5.0 release, the default full-text index directory had a hard-coded subdirectory name, as shown in the following example: "JazzTeamServer\server\conf\ccm\indices\workitemindex\fulltext_index"
However, a conflict occurred if multiple applications, for example CCM and QM, configured their full-text index directories to be the same folder. For details, see Work Item 285962. To avoid these conflicts, a unique identifier that is specific to each application is now used, as shown in the following example: "JazzTeamServer\server\conf\ccm\indices\workitemindex\_rgHxIpTTEeOSIqepiraiyw"
ISPF client
New ISPF client action to edit flow targets
The Edit Repository Workspace panel now contains an option to edit the flow targets of a repository workspace. In the Edit Flow Target panel, you can select which components flow to and flow from the selected flow target.
Detect and display the default language definition in the zFile information panel
You can now detect and display the default language definition that is associated with the file extension that is used during a build. You can change the language definition that is associated with the selected zFile by using the action field beside the language definition. The browse action code proposes a language definition list, from which you can select a language definition to associate with the zFile by typing a forward slash (/).
Jazz source control
Fill-the-gap feature
Eclipse client
A new workflow for accepting change sets into a workspace is available. When a gap is encountered, the server attempts to provide a list of missing change sets that are required to fill the gap. The user can then decide how to proceed.
Command-Line Interface
A new workflow is now availabe for accepting change sets into a workspace. For the command-line interface, a new list subcommand called missing-changesets is added.
Two new options, accept-missing-changesets and resume-missing-changesets, are added to the accept and resume commands respectively. If a gap is found, the missing changes sets required to fill the gap are automatically included in the accept and resume operations.
scm help list
Help for: scm list
Purpose:
Lists items. You can list different items, as specified by subcommands.
Aliases: ls
Usage: scm list [subcommand] [args]
Use scm help list [subcommand] to get detailed help for a list subcommand
Subcommands:
baselines - Lists baselines.
changes - Lists the changes that are in the change sets.
changesets - Lists the change sets that are in the repository.
components - Lists the components that are in a workspace, stream, or
repository.
connections - Lists the connections that were stored by the 'scm
login' command.
daemons - Lists the user's running daemons.
flowtargets - List flow targets of the workspace or stream.
locks - Lists the locks that are held in a stream.
merge-queue - Lists the change sets in the merge queue of the
component.
missing-changesets - List the additional change sets required to accept in
order to avoid merging the change sets specified.
preferences - Lists the command line client preferences.
projectareas - Lists project areas.
remotefiles - Displays the file tree of a repository workspace.
snapshots - Lists the snapshots that are associated with a workspace
or stream.
states - Lists the states of changes in the change set.
streams - Lists streams.
teamareas - Lists team areas.
users - Lists users.
workspaces - Lists repository workspaces.
scm help list missing-changesets
Help for: scm list missing-changesets
Purpose:
List the additional change sets required to accept in order to avoid merging
the change sets specified.
Aliases: list missing-cs, list missing
Usage: scm list missing-changesets [-w/--workspace <arg>]
[-s/--summarize-changes]
[-r/--repository-uri <arg>] [-u/--username
<arg> -P/--password <arg> | --certificate
<arg> -P/--password <arg> | --smartCard
-u/--username <arg>] [-j/--json]
[-v/--verbose] [selectors...]
selectors - List of change sets to specify.
Options:
-r, --repository-uri <arg> - The URI that specifies the location of the
repository.
-u, --username <arg> - The username for the repository.
-P, --password <arg> - The password for the repository.
--certificate <arg> - The file that contains the user's login
certificate.
--smartCard - Uses the connected smart card for
authentication.
-j, --json - Enables JSON output.
-v, --verbose - List each missing change set and all changes
for each.
-w, --workspace <arg> - The workspace or stream, as specified by its
name, alias, or UUID.
-s, --summarize-changes - List a summary of only the additional changes
by the missing change sets.
scm help accept
Help for: scm accept
Purpose:
Accepts changes into a repository workspace and also downloads the changes to
the sandbox if the operation was run from within the sandbox location. The
changes to accept can be scoped in one of four ways: all changes in a
workspace (default), all changes in a set of one of more components (using
--components), all changes in one or more baselines (using --baseline), or a
specific set of changes (by specifying the change set aliases, or UUIDs).
Usage: scm accept [-r/--repository-uri <arg>] [-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] [-i/--in-place-markers] [--no-merge]
[--accept-missing-changesets] [--flow-components]
[-o/--overwrite-uncommitted] [-q/--queue-merges]
[-s/--source <arg>] [-t/--target <arg>] [-b/--baseline |
-C/--components | -c/--changes] [selectors...]
selectors - An optional list of items to accept.
Options:
-r, --repository-uri <arg> - The URI that specifies the location of the
repository.
-u, --username <arg> - The username for the repository.
-P, --password <arg> - The password for the repository.
--certificate <arg> - The file that contains the user's login
certificate.
--smartCard - Uses the connected smart card for
authentication.
-j, --json - Enables JSON output.
-v, --verbose - Shows more information.
-d, --directory <arg> - Runs the command in the named directory.
-N, --no-local-refresh - Does not scan the file system for new
changes. This option overrides the value
of the refresh.local.changes preference.
To see the current value of this
preference, run 'lscm get preference
refresh.local.changes'.
-i, --in-place-markers - Modifies files that have content conflicts
to include the conflicted regions.
--no-merge - Disables automatic merging of conflicts.
--accept-missing-changesets - Automatically find change sets that are
required to avoid merging and accept them
in addition.
--flow-components - Accepts the additions and deletions of
components when the source is the current
flow target. Otherwise has no effect.
-o, --overwrite-uncommitted - Accepts changes even if uncommitted local
changes exist. If you use this option,
changes might be overwritten.
-q, --queue-merges - Allows change sets with gaps to be
accepted in repository workspace. If a
merge is already in progress, change sets
will be queued.
-s, --source <arg> - Selects the source workspace or stream
from which the changes will flow. To
specify the workspace or stream, use its
name[@repo], alias, or UUID[@repo].
-t, --target <arg> - Selects the target workspace into which
the changes will flow. To specify the
workspace, use its name[@repo], alias, or
UUID[@repo].
-b, --baseline - Indicates that the selectors refer to
baselines and the specified baselines
must be accepted. To specify a baseline,
use its name, alias, or UUID in the list
of selectors.
-C, --components - Indicates that the selectors refer to
components and all of the changes in the
specified components must be accepted. To
specify a component, use its name, alias,
or UUID in the list of selector.
-c, --changes - Indicates that the selectors refer to
change sets and only the specified change
sets must be accepted. To specify a
change set, use its alias or UUID[@repo]
in the list of selectors.
scm help resume changeset
Help for: scm resume changeset
Purpose:
Resumes change sets into a workspace from the stored suspended set that is on
the server.
Aliases: resume cs
Usage: scm resume changeset [-r/--repository-uri <arg>] [-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]
[-i/--in-place-markers] [--no-merge]
[-o/--overwrite-uncommitted] [-q/--queue-merges]
[--resume-missing-changesets] [-t/--target <arg>]
<changes...>
changes - An optional list of change sets to resume. To specify the change
sets, use alias or UUID[@repo].
Options:
-r, --repository-uri <arg> - The URI that specifies the location of the
repository.
-u, --username <arg> - The username for the repository.
-P, --password <arg> - The password for the repository.
--certificate <arg> - The file that contains the user's login
certificate.
--smartCard - Uses the connected smart card for
authentication.
-j, --json - Enables JSON output.
-v, --verbose - Shows more information.
-d, --directory <arg> - Runs the command in the named directory.
-N, --no-local-refresh - Does not scan the file system for new
changes. This option overrides the value
of the refresh.local.changes preference.
To see the current value of this
preference, run 'lscm get preference
refresh.local.changes'.
-i, --in-place-markers - Modifies files that have content conflicts
to include the conflicted regions.
--no-merge - Disables automatic merging of conflicts.
-o, --overwrite-uncommitted - Resumes change sets even if uncommitted
local changes exist. If you use this
option, changes might be overwritten.
-q, --queue-merges - Allows change sets with gaps to be
accepted in repository workspace. If a
merge is already in progress, change sets
will be queued.
--resume-missing-changesets - Automatically find change sets that are
required to avoid merging and resume them
in addition.
-t, --target <arg> - Selects a target workspace that changes
will be resumed into. To specify the
target workspace, use its name[@repo],
alias, or UUID[@repo].
Client for Microsoft Visual Studio IDE
A new workflow is available for accepting change sets into a workspace. When a gap is encountered, the server attempts to provide a list of missing change sets that are required to fill the gap. The user can then decide how to proceed.
Duplicate a stream or workspace (command-line interface)
The "create stream" and "create workspace" commands can now duplicate a stream or workspace.
scm help create stream
Help for: scm create stream
Purpose:
Creates a stream in the repository. If you specify a flow target or snapshot,
the stream is populated with the components of that stream or snapshot.
Aliases: create st, create s
Usage:
scm create stream [-r/--repository-uri <arg>] [-u/--username <arg>
-P/--password <arg> | --certificate <arg> -P/--password
<arg> | --smartCard -u/--username <arg>] [-j/--json]
[-d/--description <arg>] [-s/--stream <arg> | --snapshot
<arg>] (--projectarea | --teamarea) <name> <owner>
scm create stream [-r/--repository-uri <arg>] [-u/--username <arg>
-P/--password <arg> | --certificate <arg> -P/--password
<arg> | --smartCard -u/--username <arg>] [-j/--json]
--duplicate <arg> <name>
name - The name of the stream.
owner - The project area or team area that owns the stream, indicated by
using either the --projectarea or --teamarea option. To specify the
project area or team area, use its name, alias, or UUID.
Options:
-r, --repository-uri <arg> - The URI that specifies the location of the
repository.
-u, --username <arg> - The username for the repository.
-P, --password <arg> - The password for the repository.
--certificate <arg> - The file that contains the user's login
certificate.
--smartCard - Uses the connected smart card for
authentication.
-j, --json - Enables JSON output.
-d, --description <arg> - The description of the workspace/stream.
-s, --stream <arg> - The stream or workspace to use as the initial
stream history. To specify the stream or
workspace, use its name[@repo], alias, or
UUID[@repo].
--snapshot <arg> - The snapshot to use as the initial stream
history. To specify the snapshot, use its
name[@repo], alias, or UUID[@repo].
--projectarea - Indicates that the owner of the stream is a
project area.
--teamarea - Indicates that the owner of the stream is a
team area.
--duplicate <arg> - Stream to duplicate. To specify the stream, use
name[@repo], alias or UUID[@repo].
scm help create workspace
Help for: scm create workspace
Purpose:
Creates a repository workspace. If you specify a flow target or snapshot, the
repository workspace will be populated with the components of that stream or
snapshot.
Aliases: create ws, create w
Usage:
scm create workspace [-r/--repository-uri <arg>] [-u/--username <arg>
-P/--password <arg> | --certificate <arg> -P/--password
<arg> | --smartCard -u/--username <arg>] [-j/--json]
[-d/--description <arg>] [-s/--stream <arg> | --snapshot
<arg> | -e/--empty] <name>
scm create workspace [-r/--repository-uri <arg>] [-u/--username <arg>
-P/--password <arg> | --certificate <arg> -P/--password
<arg> | --smartCard -u/--username <arg>] [-j/--json]
--duplicate <arg> <name>
name - The name of the workspace.
Options:
-r, --repository-uri <arg> - The URI that specifies the location of the
repository.
-u, --username <arg> - The username for the repository.
-P, --password <arg> - The password for the repository.
--certificate <arg> - The file that contains the user's login
certificate.
--smartCard - Uses the connected smart card for
authentication.
-j, --json - Enables JSON output.
-d, --description <arg> - The description of the workspace/stream.
-s, --stream <arg> - The stream or workspace to set as the default
flow target and initial workspace history. To
specify the stream or workspace, use its
name[@repo], alias, or UUID[@repo].
--snapshot <arg> - The snapshot to use as the initial workspace
history. To specify the snapshot, use
name[@repo], alias, or UUID[@repo].
-e, --empty - Creates an empty workspace. Default component
will not be created for the workspace.
--duplicate <arg> - Workspace to duplicate. To specify the
workspace, use name[@repo], alias or
UUID[@repo].
Auto-merge during the resume and resolve operations (command-line interface)
The "resume changeset" and "resolve conflict" commands are updated to automatically merge non-conflicting changes and add in-place markers for conflicting changes.
scm help resume changeset
Help for: scm resume changeset
Purpose:
Resumes change sets into a workspace from the stored suspended set that is on
the server.
Aliases: resume cs
Usage: scm resume changeset [-r/--repository-uri <arg>] [-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]
[-i/--in-place-markers] [--no-merge]
[-o/--overwrite-uncommitted] [-q/--queue-merges]
[--resume-missing-changesets] [-t/--target <arg>]
<changes...>
changes - An optional list of change sets to resume. To specify the change
sets, use alias or UUID[@repo].
Options:
-r, --repository-uri <arg> - The URI that specifies the location of the
repository.
-u, --username <arg> - The username for the repository.
-P, --password <arg> - The password for the repository.
--certificate <arg> - The file that contains the user's login
certificate.
--smartCard - Uses the connected smart card for
authentication.
-j, --json - Enables JSON output.
-v, --verbose - Shows more information.
-d, --directory <arg> - Runs the command in the named directory.
-N, --no-local-refresh - Does not scan the file system for new
changes. This option overrides the value
of the refresh.local.changes preference.
To see the current value of this
preference, run 'lscm get preference
refresh.local.changes'.
-i, --in-place-markers - Modifies files that have content conflicts
to include the conflicted regions.
--no-merge - Disables automatic merging of conflicts.
-o, --overwrite-uncommitted - Resumes change sets even if uncommitted
local changes exist. If you use this
option, changes might be overwritten.
-q, --queue-merges - Allows change sets with gaps to be
accepted in repository workspace. If a
merge is already in progress, change sets
will be queued.
--resume-missing-changesets - Automatically find change sets that are
required to avoid merging and resume them
in addition.
-t, --target <arg> - Selects a target workspace that changes
will be resumed into. To specify the
target workspace, use its name[@repo],
alias, or UUID[@repo].
scm help resolve conflict
Help for: scm resolve conflict
Purpose: Resolves workspace conflicts.
Aliases: resolve cft, resolve change, resolve ch
Usage:
scm resolve conflict [-r/--repository-uri <arg>] [-u/--username <arg>
-P/--password <arg> | --certificate <arg> -P/--password
<arg> | --smartCard -u/--username <arg>] [-d/--directory
<arg>] [-N/--no-local-refresh]
[-o/--overwrite-uncommitted] (-p/--proposed |
-c/--checkedin) <path...>
scm resolve conflict [-r/--repository-uri <arg>] [-u/--username <arg>
-P/--password <arg> | --certificate <arg> -P/--password
<arg> | --smartCard -u/--username <arg>] [-d/--directory
<arg>] [-N/--no-local-refresh]
[-o/--overwrite-uncommitted] [-i/--in-place-markers]
-a/--auto-merge
path - The alias, UUID or path of the items to resolve.
Options:
-r, --repository-uri <arg> - The URI that specifies the location of the
repository.
-u, --username <arg> - The username for the repository.
-P, --password <arg> - The password for the repository.
--certificate <arg> - The file that contains the user's login
certificate.
--smartCard - Uses the connected smart card for
authentication.
-d, --directory <arg> - Specifies the root of the shared file system.
-N, --no-local-refresh - Does not scan the file system for new changes.
This option overrides the value of the
refresh.local.changes preference. To see the
current value of this preference, run 'lscm
get preference refresh.local.changes'.
-o, --overwrite-uncommitted - Continues with the operation even if
uncommitted local changes exist. If you use
this option, changes might be overwritten.
-p, --proposed - Resolves conflicts by using the proposed
version.
-c, --checkedin - Resolves conflicts by using the currently
checked in version.
-i, --in-place-markers - Modifies files that have content conflicts to
include the conflicted regions.
-a, --auto-merge - Merge the conflicts automatically.
Highlight common ancestor for conflicts (Eclipse client)
When the history is shown for a file that has a conflict, the common ancestor and the two end states for the conflict are now highlighted in the history view. The user can see which changes conflict and what the branch point is.
Required migration of existing databases
A major refactoring of the server model now includes advanced features in Rational Team Concert 5.0 and later releases. Because it requires a migration to run on existing databases, online migration can be used to reduce server down time with some additional "offline" time required to run addTables. Details on performing the migration, estimating migration time, and verifying migration results can be found at this link.
Version ID feature
In Rational Team Concert 5.0, all new versions of SCM-controlled files are assigned a version ID. The version ID is unique for any version of the same file.
For different use cases, the version ID can be displayed in two forms. The simple form is a numeric string that uniquely identifies a file version within a repository. If you use distributed SCM and make changes to the same file in multiple repositories, you might want to use the full version ID, which uniquely identifies a file version across all repositories. This identifier is needed when users make parallel changes to the same file in multiple repositories because those files might be assigned with the same simple version number. The full version ID is guaranteed to be unique for a file version across all repositories.
Eclipse client
The version ID is available in the following Eclipse views:
History view
A version ID column is added to the history view and the check-in history view. The version ID column can be turned on or off in the history view similar to other columns. By default, the version ID column is on.
Repository File Explorer view
Version ID information can be displayed in the File Repository Explorer view, but it is turned off by default. This option can be turned on by changing the Eclipse preference settings.
Change Explorer view
Version ID information can be displayed in the Change Explorer view as well, and is turned off by default. This option can be turned on by changing the Eclipse preference settings.
Change Summary view
Version ID information can also be displayed in the Change Summary view, and is turned off by default. This option can be turned on by changing the Eclipse preference settings.
Change Version Identifier display options
Users can change where and how the version ID is displayed on the Eclipse User Preference page. Users can individually turn on or turn off version ID information for the Change Explorer, Change Summary, and Repository Files views.
Users can also change the display format of the version IDs.
Command-line client
Version IDs can be used by the following CLI commands.
lscm list remotefiles command
Users can use the lscm list remotefiles command to show version ID information for the files that are used in a workspace, stream, baseline, or snapshot.
Usage: lscm list remotefiles ... [-i/--show-versionid [arg]] ...
-i, --show-versionid [arg] - Show version ID for files. Specify 'full' to
show the full version ID.
Example:
C:\RTC-CLI\eclipse>lscm list remotefiles --show-versionid --depth - -w "My Project Area Stream Workspace" "My Project Area Default Component" "/" -r https://localhost:9443/jazz -u ADMIN -P ADMIN
/
/Hello World/
/Hello World/.classpath [1]
/Hello World/.project [1]
/Hello World/.settings/
/Hello World/.settings/org.eclipse.jdt.core.prefs [1]
/Hello World/src/
/Hello World/src/test/
/Hello World/src/test/HelloWorld.java [4]
lscm get file command
Users can also use version IDs in the lscm get file command to extract file contents.
Usage: lscm get file ... (-b/--baseline <baseline> | -w/--workspace <workspace> |
-s/--snapshot <snapshot> | <item>) [-c/--component <arg>]
[-f/--filepath <arg>] <state> <path-on-disk>
state - The state id or version ID of the item to be extracted.
Options:
-b, --baseline - The baseline (name[@repo], alias, or
UUID[@repo]) that contains the file.
-w, --workspace - The workspace or stream (name[@repo], alias, or
UUID[@repo]) that contains the file.
-s, --snapshot - The snapshot (name[@repo], alias, or
UUID[@repo]) that contains the file.
-c, --component <arg> - The component for which the files are listed.
Must used with "-b", "-w", or "-s" options.
-f, --filepath <arg> - The files path. Must used with "-b", "-w", or
"-s" options.
Example:
Get version 4 of the HelloWorld.java file:
(MSDEV) C:\RTC-CLI\eclipse>lscm get file -w "My Project Area Stream Workspace" -c "My Project Area Default Component" -f "/Hello World/src/test/HelloWorld.java" 4 -o c:\t1 -r https://localhost:9443/jazz -u ADMIN -P ADMIN
Successfully extracted file to "C:\t1".
Visual Studio client
Version ID information is also available in the Visual Studio client, similar to the Eclipse client. Turn the display of version IDs on or off for different Visual Studio client views from the Options dialog.
Accept and deliver work items
The accept and deliver commands are updated with a new --workitems option to accept and deliver changes from a work item. The accept command accepts changes to components in the source workspace or stream. The deliver command delivers outgoing changes from the workspace to the flow target.
Usage:
scm accept [-c/--changes | -b/--baseline | -C/--components] [-s/--source <arg>]
[-t/--target <arg>] [-r/--repository-uri <arg>] [-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]
[-i/--in-place-markers] [--no-merge] [--accept-missing-changesets]
[--flow-components] [-o/--overwrite-uncommitted]
[-q/--queue-merges] [selectors...]
scm accept [-W/--workitems] [-t/--target <arg>] [-r/--repository-uri <arg>]
[-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]
[-i/--in-place-markers] [--no-merge] [--accept-missing-changesets]
[--flow-components] [-o/--overwrite-uncommitted]
[-q/--queue-merges] [selectors...]
selectors - An optional list of items to accept.
Options:
-W, --workitems - Indicates that the selectors refer to work
items and all the change sets must be
accepted. To specify a work item, use its
ID[@repo] in the list of selectors. To
selectively specify the change sets of a
work item, list the change sets of the
work item and specify the change sets
with --changes option.
Usage:
scm deliver [-c/--changes | -b/--baselines | -C/--components] [-s/--source
<arg>] [-t/--target <arg>] [-r/--repository-uri <arg>]
[-u/--username <arg> -P/--password <arg> | --certificate <arg>
-P/--password <arg> | --smartCard -u/--username <arg>] [-j/--json]
[-v/--verbose] [-d/--directory <arg>] [-q/--quiet]
[-N/--no-local-refresh] [-i/--ignore-uncommitted]
[-h/--harmonize-history] [selectors...]
scm deliver [-W/--workitems] [-s/--source <arg>] [-r/--repository-uri <arg>]
[-u/--username <arg> -P/--password <arg> | --certificate <arg>
-P/--password <arg> | --smartCard -u/--username <arg>] [-j/--json]
[-v/--verbose] [-d/--directory <arg>] [-q/--quiet]
[-N/--no-local-refresh] [-i/--ignore-uncommitted]
[-h/--harmonize-history] [selectors...]
selectors - An optional list of items to deliver.
Options:
-W, --workitems - Indicates that the selectors refer to work
items and all the change sets in the specified
work items must be delivered. To specify a
work item, use its ID[@repo] in the list of
selectors.
Support for configuring external compare tools
The scm command line now supports configuring an external two-way and three-way compare tool in the preferences. The external compare tool can be launched in the diff, show conflicts, and resolve conflict commands by using the --xcompare option. The diff command compares a local file with a file in the workspace, stream, snapshot, baseline, or change set. The external compare tool shows only content differences.
Usage: scm diff [-r/--repository-uri <arg>] [-u/--username <arg> -P/--password
<arg> | --certificate <arg> -P/--password <arg> | --smartCard
-u/--username <arg>] [-d/--directory <arg>]
[-N/--no-local-refresh] [-w/--workspace <arg>] [-c/--component
<arg>] [[-x/--xcompare] [-S/--show <arg>] | [-p/--fullpatch]]
<after-type> <after-selector> [before-type] [before-selector]
after-type - Type of the item to use for the after state (file,
workspace, stream, baseline, changeset, snapshot).
after-selector - Selector of the item to use for the after state(path of the
the file on disk, name[@repo], alias or UUID[@repo]).
before-type - Type of the item to use for the before state (workspace,
stream, baseline, changeset, snapshot).
before-selector - Selector of the item to use for the before
state(name[@repo], alias or UUID[@repo]).
Options:
-x, --xcompare - Opens an external compare tool that is
configured in the preferences. This tool shows
only content differences.
Usage:
scm show conflicts [-m/--mine <arg> | -p/--proposed <arg> | -a/--ancestor
<arg>] [--content] [--all-properties | --property-names |
--property-name <arg>] [-j/--json] [-q/--quiet]
[-r/--repository-uri <arg>] [-u/--username <arg>
-P/--password <arg> | --certificate <arg> -P/--password
<arg> | --smartCard -u/--username <arg>] [-d/--directory
<arg>]
scm show conflicts [-x/--xcompare <arg>] [-r/--repository-uri <arg>]
[-u/--username <arg> -P/--password <arg> | --certificate
<arg> -P/--password <arg> | --smartCard -u/--username
<arg>] [-d/--directory <arg>]
Options:
-x, --xcompare <arg> - The alias, UUID, or path of the item that has
conflicts. Opens an external compare tool that
is configured in the preferences. This tool
shows only content differences.
Usage:
scm resolve conflict [-r/--repository-uri <arg>] [-u/--username <arg>
-P/--password <arg> | --certificate <arg> -P/--password
<arg> | --smartCard -u/--username <arg>] [-d/--directory
<arg>] [-N/--no-local-refresh]
[-o/--overwrite-uncommitted] (-p/--proposed |
-c/--checkedin) <path...>
scm resolve conflict [-r/--repository-uri <arg>] [-u/--username <arg>
-P/--password <arg> | --certificate <arg> -P/--password
<arg> | --smartCard -u/--username <arg>] [-d/--directory
<arg>] [-N/--no-local-refresh] [-i/--in-place-markers]
-a/--auto-merge
scm resolve conflict [-r/--repository-uri <arg>] [-u/--username <arg>
-P/--password <arg> | --certificate <arg> -P/--password
<arg> | --smartCard -u/--username <arg>] [-d/--directory
<arg>] -x/--xcompare <arg>
path - The alias, UUID or path of the items to resolve.
Options:
-x, --xcompare <arg> - The alias, UUID, or path of the item that has
conflicts. Opens an external compare tool
that is configured in the preferences. This
tool shows only content differences.
$ lscm list pref -v
...
...
Name : external.compare.2way
Description : External 2-way compare tool
Format: <full path to the executable> <options>
Note: Some characters such as " or $ might have a special meaning in certain operating systems and you might need to be escape characters
to represent them.
Examples:
external.compare.2way: <bcompare path> -title1="" -title2="" -rightreadonly
external.compare.2way: <xcleardiff path>
external.compare.2way: <diffmerge path> -ro1 -title2="" -title1=""
external.compare.2way: <kdiff3 path> --L1 "" --L2 "" --output
external.compare.2way: <p4merge path> -nl "" -nr ""
external.compare.2way: <winmerge path> -dl "" -dr "" -wr /e /u
Default Value : None
Current Value : None
Name : external.compare.3way
Description : External 3-way compare tool
Format: <full path to the executable> <options>
This tool compares items that have conflicts. If this tool is not configured, the 2-way compare tool is used by default.
Examples:
Note: Some characters such as " or $ might have a special meaning in certain operating systems and you might need to be escape characters
to represent them.
external.compare.3way: <bcompare path> -title1=""
-title2="" -title3="" -title4=""
external.compare.3way: <xcleardiff path> -base "" -out "" ""
external.compare.3way: <diffmerge path> -result="" -title1="" -title2=""
-title3=""
external.compare.3way: <kdiff3 path> --L1 "" --L2 "" --L3
"" --output
external.compare.3way: <p4merge path> -nb "" -nl "" -nr "" -nm ""
Default Value : None
Current Value : None
Customizing the behavior of Jazz source control operations from the browser
Currently, the behavior for the source control operations can be configured only from the Eclipse client. This new feature enables project administrators to configure the behavior for the source-control operations from the browser itself. Users can add, configure, and remove the preconditions and follow-up actions for all the source control operations, except deliver (client).
Rational Team Concert Git integration
Introduction to the Git integration
With this release, Rational Team Concert can be used for process enforcement and change management in teams that use Git as a source control management (SCM) tool. You now have a single and centralized way of enforcing the process across teams that use heterogeneous SCM systems (like Rational Team Concert and Git). The two main features implemented are:
- Process enforcement for Git SCM operations
- Linking Rational Team Concert work items with Git commits
For more information, click Source Control > Work with Git in the Rational Team Concert web client.
This integration is supported for basic Git and Gerrit repositories.
Process enforcement for Git SCM operations
Git specific permissions and pre-conditions can be triggered for Git push operations, so you can control and customize how commits are pushed to a Git repository that is managed in Rational Team Concert.
Git Permissions Configuration
Git Pre-conditions Configuration
After the Git repository is registered, Rational Team Concert checks the validity of the Git "push" against the configured permissions and pre-conditions. The push operation fails if the appropriate permissions and pre-conditions are not met, and you are notified about the error.
Linking Rational Team Concert work items with Git commits
A Git commit can be linked to a Rational Team Concert work item. The commit link is under the "Change Sets (Remote)" group in the Links tab of the work item. The basic information about the Git commit is displayed when you hover the mouse pointer over the link.
Rational Team Concert reports
Average lead time
This report plots the trend for the average time that work items stay in the unresolved state.
Average cycle time
This report plots the trend of the average time that work items stay in the inactive state.
Process control
The report plots the time that work items are in the unresolved state.
Cycle time as percentage of lead time
This report plots the trend of the active time as a percentage of the unresolved time for work items.
Average time in state
This report plots the average time that work items spend in a particular state.
Burndown by story points
This report displays the remaining story points.
Burnup by story points
This report displays the completed story points.
Tracking and planning
Dragging OSLC work item links in plans
OSLC work item links such as Related Change Request/External, Tracks/Contributes To, and Affects Plan Item/Affected By Defect can now be created between two existing items with drag and drop in the plan web UI for items in the same project. For example:
- Configure the tree display of the plan to use the link type. For example, Tracks -> Contributes To.
- Items on the same project can be dropped on an item to build the hierarchy, dropped as a sibling, or dropped on a group using the link type that is configured for the tree display.
You can also drag these OSLC work item links that are shown in a plan across projects to another item in the plan to change their hierarchy.
Usability improvements to the Plan Search page
Plan search results can now be filtered by keywords directly on the page, helping you find the plans you care about faster. Additionally, the All Plans page can now be filtered by team area.
The Plan Search page now has tabs for easy navigation between My Current Plans, Current Plans, and All Plans.
Plan progress bars are now hidden by default in plan search results. They can be displayed by clicking Show Progress on the page.
The Welcome to Plans page now features a search field that you can use to search the project area plans. You can limit the search to current plans or only current plans that are associated with team areas that you belong to.
Clicking the Team area or Project Area in the owner column of the search results now filters the plan results to only that team or project area.
The Plan Search page now includes a first and last button in the pagination control. The page also scrolls the search results filter controls with the page view to provide a reference and control when scrolling through large search results.
Work item editor performance improvements
The work item editor loads faster because content caching is more efficient and fewer network requests are required to load a work item. For more information, see Web Caching Performance improvements in 5.0 CCM.