Known limitations and workarounds in this release

This release of the ClearCase® Connector has the following limitations and restrictions.
Edition note: The feature described here applies to Rational Team Concert™ Standard edition and Enterprise edition only.
Migration
  • When migrating from Rational Team Concert version 1.x, you must upgrade your ClearCase Synchronized Streams, using the upgradeSyncStream command, in order for synchronizations to continue running correctly. Perform this upgrade from each synchronization host after you install the new version of the ClearCase Connector but before you start the synchronization engine. To do so, open a command line and run the ccc upgradeSyncStream command. For each synchronization stream specified, this command changes the default buildkind from ant to the command line and copies the credentials file for the synchronization engine to each stream's specific subdirectory. See Upgrading synchronization streams when migrating from Rational Team Concert version 1.x.
Considerations
  • Only Rational® ClearCase 7.0.0 and later releases are supported.
  • ClearCase identities cannot be synchronized with Jazz identities because ClearCase identities, which are operating system login names, do not map to Jazz identities, which are users in the Jazz repository and usually imported from LDAP.
  • To be imported from a UCM stream, a file or folder must be a member of a UCM component. The root folder of a multi-component UCM VOB is not a member of any UCM component, and cannot be imported.
  • Change sets created to import changes from a base Rational ClearCase branch that has been enabled for Rational ClearQuest® are not annotated with Rational ClearQuest changed-activity information.
  • When working in Rational ClearCase with resources that are part of a synchronized stream, observe the guidelines in Considerations for Rational ClearCase users.
Limitations
  • The ClearCase Synchronized Streams view can sometimes report a synchronization success or failure before the Build Results have been updated. To work around this problem, right-click the stream and click Latest Synchronization Details. Refresh the build Summary page to update the synchronization status.
  • When you change the Jazz Provider Properties of a ClearCase Synchronized Stream, you might see a Save workspace failed message in the Team Advisor view. You can ignore the message.
  • Sometimes the synchronization engine's window disappears immediately after an error message appears, which prevents you from reading the message. When that occurs you can create a script to run the Jazz Build Engine in an existing window. Create this script by completing the following steps:
    1. Locate the synchronization startup script. The location of the directory that contains the script is displayed in the Jazz Provider Properties page as the value of the SCRIPT_LOCATION_PREFIX argument. The script has the same name as the synchronization stream. For example, script_location_prefix_value/synchronization_stream_name
    2. Create a copy of the script.
    3. Edit the copy by removing the first few words, up to the pathname to the Jazz Build Engine.
    4. Run the copy of the script
    When the Jazz Build Engine reports an error and exits, the messages now appear in the window in which you ran the script.
  • If a post-op checkout trigger fails, but the checkout was otherwise successful, the cleartool operations will complete successfully but issue errors to stderr. So a failed post-op trigger will cause the sync to fail, even if the command that triggered the post-op trigger succeeded.

Feedback

Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug