How to force a comment in the CC Sync checkin commandline

Go to the sync stream view, and select the "properties" operation on the
sync stream.
In the properties view, select the "ClearCase" page.
In the CHECKIN_COMMENT property, type in some string (that string will
then be used as the checkin comment for that sync stream).

Cheers,
Geoff

timothy.mulligan wrote:

We are setting up ClearCase Synchronization and the checkins in
ClearCase are failing due to a trigger that we have attached to all
of our VOBs which force a comment to be entered at time of checkin.
We noticed that the CC Sync specifies '-nc' on the cleartool checkin
commandline. Is there any way to alter this behavior and force a
comment such as the Change Set ID or Change Set Description?

Great! Thank you Geoff ...

One follow-up question. Is there a system property that contains the change set IDs that are being sync'd to ClearCase? In other words, rather than setting a generic comment such as "Synchronizer changes from RTC", ideally we would like to add traceability value into the comment and include the RTC change set IDs involved.
Thanks again,
-Tim

We have the same problem. We need to copy the RTC changeset comment to ClearCase when checking in. Anybody knows how to do this? Thanks.

Lin

One follow-up question. Is there a system property that contains the change set IDs that are being sync'd to ClearCase? In other words, rather than setting a generic comment such as "Synchronizer changes from RTC", ideally we would like to add traceability value into the comment and include the RTC change set IDs involved.
Thanks again,
-Tim

Sorry Tim, somehow I missed this question. (Raistlin, thanks for
re-raising it!)

Please look at the on-line help section:

Integrating > Rational Team Concert and Rational ClearCase > Using the
ClearCase Connector for Rational Team Concert source control >
Configuring and using the ClearCase Synchronizer > Synchronizing
Using ClearCase triggers during synchronization

In particular, in there it says:

The ClearCase Synchronizer includes an environment variable that makes
it possible to use work item information in ClearCase triggers. During
each synchronization, the list of Jazz work items that are associated
with changes that are being synchronized to Rational ClearCase are made
available in the environment variable CCASE_JAZZ_WORK_ITEMS. Rational
ClearCase users can use this variable in triggers that perform ClearCase
actions. For example, a trigger can add the list of work items to
check-in comments in Rational ClearCase or a trigger can create
attributes for the work item information on new ClearCase versions
created during the synchronization.

So you can't get change-set ID's, but you can get work item ID's.

Cheers,
Geoff


On 4/6/2010 12:52 PM, timothy.mulligan wrote:

One follow-up question. Is there a system property that contains the
change set IDs that are being sync'd to ClearCase? In other words,
rather than setting a generic comment such as "Synchronizer
changes from RTC", ideally we would like to add traceability
value into the comment and include the RTC change set IDs involved.
Thanks again,
-Tim

You can get the work item ID's (please see the belated response to Tim's
original question), but you cannot currently get the change set
comments. The idea is that the work item ID's are the most succinct way
of capturing all the information in a way that lets you easily traverse
(in RTC) to the rest of the information.

If you really need the change set comments in the CC checkin comment,
please open an enhancement request for the ClearCase Connector category.

Cheers,
Geoff

On 5/20/2010 9:38 AM, Raistlin wrote:

We have the same problem. We need to copy the RTC changeset comment to
ClearCase when checking in. Anybody knows how to do this? Thanks.

Lin


timothy.mulliganwrote:
One follow-up question. Is there a system property that contains the
change set IDs that are being sync'd to ClearCase? In other words,
rather than setting a generic comment such as "Synchronizer
changes from RTC", ideally we would like to add traceability
value into the comment and include the RTC change set IDs involved.
Thanks again,
-Tim