Automatically accept changes delivered from ClearCase

You could use the RTC "build" machinery to automatically schedule such a
process, and use the RTC command line to perform this action. But note
that this automatic deliver process might fail if parallel changes have
occurred between RTC and ClearCase, as indicated by the "conflict"
status that will appear on the sync stream.

Terminological note: you "deliver" changes to a stream, not accept them
into it.

Cheers,
Geoff

yisu wrote:

Hello,

One of my client asking this:

He has CC sync stream runs every hour, If there are changes in the RTC
stream it synchs them to the ClearCase branch and checks in a new
version on that branch. If there are changes to the ClearCase
branch, the synch job copies them to RTC as Incoming Changes, where
they have to be MANUALLY accepted into the stream. He wants to know
if there is a way to AUTOMATICALLY Accept those changes into the
Synchronized stream without performing a MANUAL Accept. Thanks for
any response in advanced.

Susan

Jazz/RTC Support

Hi Geoff,

Thanks for your response. Could you please elaborate further on how to use the RTC build machinery to automate such a process? Currently, updates sync from ClearCase are pending in the RTC clone workspace as incoming change set and don't get delivered to the CC sync stream until client manually accept the changes... How do we automate this process by using the rtc build machine? Client understands if there conflicts, they will be placed to the merge workspace and will not get delivered to the cc sync stream until they are resolved. Thanks.

Susan

You could use the RTC "build" machinery to automatically schedule such a
process, and use the RTC command line to perform this action. But note
that this automatic deliver process might fail if parallel changes have
occurred between RTC and ClearCase, as indicated by the "conflict"
status that will appear on the sync stream.

Terminological note: you "deliver" changes to a stream, not accept them
into it.

Cheers,
Geoff

yisu wrote:

Hello,

One of my client asking this:

He has CC sync stream runs every hour, If there are changes in the RTC
stream it synchs them to the ClearCase branch and checks in a new
version on that branch. If there are changes to the ClearCase
branch, the synch job copies them to RTC as Incoming Changes, where
they have to be MANUALLY accepted into the stream. He wants to know
if there is a way to AUTOMATICALLY Accept those changes into the
Synchronized stream without performing a MANUAL Accept. Thanks for
any response in advanced.

Susan

Jazz/RTC Support

I should have read your original request more carefully ... please
ignore my original response (:-). Corrected response:

The changes from ClearCase are applied directly by the synchronizer to
the clone workspace, so they wouldn't ever show up as Pending Changes to
the clone workspace (and a user should never be loading the clone
workspace into your pending changes view anyway ... that's a private
workspace for use just by the synchronizer).

In general, the sync process automatically delivers changes from the
clone workspace to the sync stream unless there are conflicts. So if
there are no conflicts, then the user should see those changes from
ClearCase automatically appearing in the sync stream when the sync
completes.

To make sure there has been no misunderstanding between you and the
customer, make sure that they clearly identify what workspace they have
loaded in their Pending Changes view. It is reasonable for them to load
the Merge Workspace into the Pending Changes view (to confirm there
really are no conflicts).

Cheers,
Geoff

yisu wrote:

Hi Geoff,

Thanks for your response. Could you please elaborate further on how
to use the RTC build machinery to automate such a process?
Currently, updates sync from ClearCase are pending in the RTC clone
workspace as incoming change set and don't get delivered to the CC
sync stream until client manually accept the changes... How do we
automate this process by using the rtc build machine? Client
understands if there conflicts, they will be placed to the merge
workspace and will not get delivered to the cc sync stream until they
are resolved. Thanks.

Susan




gmclemmwrote:
You could use the RTC "build" machinery to automatically
schedule such a
process, and use the RTC command line to perform this action. But
note
that this automatic deliver process might fail if parallel changes
have
occurred between RTC and ClearCase, as indicated by the
"conflict"
status that will appear on the sync stream.

Terminological note: you "deliver" changes to a stream,
not accept them
into it.

Cheers,
Geoff

yisu wrote:
Hello,

One of my client asking this:

He has CC sync stream runs every hour, If there are changes in the
RTC
stream it synchs them to the ClearCase branch and checks in a new
version on that branch. If there are changes to the ClearCase
branch, the synch job copies them to RTC as Incoming Changes, where
they have to be MANUALLY accepted into the stream. He wants to
know
if there is a way to AUTOMATICALLY Accept those changes into the
Synchronized stream without performing a MANUAL Accept. Thanks for
any response in advanced.

Susan

Jazz/RTC Support

Hi Geoff,

I had a screen share session with the customer.. and I confirmed it is the clone workspace he has loaded to the pending change view.. and he has to manually accept changes from the pending change view to deliver the changes to the CC sync stream.. according to what you described, was it because he loaded the clone workspace to the pending change view so he has to manually accept? And if he unload that workspace, changes will get delivered automatically? please verify.. thanks.

Susan

I should have read your original request more carefully ... please
ignore my original response (:-). Corrected response:

The changes from ClearCase are applied directly by the synchronizer to
the clone workspace, so they wouldn't ever show up as Pending Changes to
the clone workspace (and a user should never be loading the clone
workspace into your pending changes view anyway ... that's a private
workspace for use just by the synchronizer).

In general, the sync process automatically delivers changes from the
clone workspace to the sync stream unless there are conflicts. So if
there are no conflicts, then the user should see those changes from
ClearCase automatically appearing in the sync stream when the sync
completes.

To make sure there has been no misunderstanding between you and the
customer, make sure that they clearly identify what workspace they have
loaded in their Pending Changes view. It is reasonable for them to load
the Merge Workspace into the Pending Changes view (to confirm there
really are no conflicts).

Cheers,
Geoff

yisu wrote:

Hi Geoff,

Thanks for your response. Could you please elaborate further on how
to use the RTC build machinery to automate such a process?
Currently, updates sync from ClearCase are pending in the RTC clone
workspace as incoming change set and don't get delivered to the CC
sync stream until client manually accept the changes... How do we
automate this process by using the rtc build machine? Client
understands if there conflicts, they will be placed to the merge
workspace and will not get delivered to the cc sync stream until they
are resolved. Thanks.

Susan




gmclemmwrote:
You could use the RTC "build" machinery to automatically
schedule such a
process, and use the RTC command line to perform this action. But
note
that this automatic deliver process might fail if parallel changes
have
occurred between RTC and ClearCase, as indicated by the
"conflict"
status that will appear on the sync stream.

Terminological note: you "deliver" changes to a stream,
not accept them
into it.

Cheers,
Geoff

yisu wrote:
Hello,

One of my client asking this:

He has CC sync stream runs every hour, If there are changes in the
RTC
stream it synchs them to the ClearCase branch and checks in a new
version on that branch. If there are changes to the ClearCase
branch, the synch job copies them to RTC as Incoming Changes, where
they have to be MANUALLY accepted into the stream. He wants to
know
if there is a way to AUTOMATICALLY Accept those changes into the
Synchronized stream without performing a MANUAL Accept. Thanks for
any response in advanced.

Susan

Jazz/RTC Support

The main problem is that they apparently are logged in to the RTC
Eclipse client with the cc synchronizer account. That should never be
done. From the CC Connector On-Line Documentation:

"The synchronization process account provides Jazz repository
credentials used by the synchronization process. This account requires a
special class of client access license, and should never be used by a
team member to connect to the repository."

In particular, doing something like manually accepting changes into the
clone workspace (which RTC would have prevented, unless they log in as
the synchronization account) will break the synchronization process.

At this point, the easiest way to proceed is to have the customer create
a new synchronization stream (and make sure they never log in using the
synchronization account). If they want to keep their current
synchronization stream (because it took a long time to do the initial
import), create a jazz.net workitem, and we can walk you through that
process.

Cheers,
Geoff

yisu wrote:

Hi Geoff,

I had a screen share session with the customer.. and I confirmed it is
the clone workspace he has loaded to the pending change view.. and he
has to manually accept changes from the pending change view to
deliver the changes to the CC sync stream.. according to what you
described, was it because he loaded the clone workspace to the
pending change view so he has to manually accept? And if he unload
that workspace, changes will get delivered automatically? please
verify.. thanks.

Susan





gmclemmwrote:
I should have read your original request more carefully ... please
ignore my original response (:-). Corrected response:

The changes from ClearCase are applied directly by the synchronizer
to
the clone workspace, so they wouldn't ever show up as Pending
Changes to
the clone workspace (and a user should never be loading the clone
workspace into your pending changes view anyway ... that's a private

workspace for use just by the synchronizer).

In general, the sync process automatically delivers changes from the

clone workspace to the sync stream unless there are conflicts. So
if
there are no conflicts, then the user should see those changes from

ClearCase automatically appearing in the sync stream when the sync
completes.

To make sure there has been no misunderstanding between you and the

customer, make sure that they clearly identify what workspace they
have
loaded in their Pending Changes view. It is reasonable for them to
load
the Merge Workspace into the Pending Changes view (to confirm there

really are no conflicts).

Cheers,
Geoff

yisu wrote:
Hi Geoff,

Thanks for your response. Could you please elaborate further on
how
to use the RTC build machinery to automate such a process?
Currently, updates sync from ClearCase are pending in the RTC clone
workspace as incoming change set and don't get delivered to the CC
sync stream until client manually accept the changes... How do we
automate this process by using the rtc build machine? Client
understands if there conflicts, they will be placed to the merge
workspace and will not get delivered to the cc sync stream until
they
are resolved. Thanks.

Susan




gmclemmwrote:
You could use the RTC "build" machinery to automatically
schedule such a
process, and use the RTC command line to perform this action. But
note
that this automatic deliver process might fail if parallel changes
have
occurred between RTC and ClearCase, as indicated by the
"conflict"
status that will appear on the sync stream.

Terminological note: you "deliver" changes to a stream,
not accept them
into it.

Cheers,
Geoff

yisu wrote:
Hello,

One of my client asking this:

He has CC sync stream runs every hour, If there are changes in the
RTC
stream it synchs them to the ClearCase branch and checks in a new
version on that branch. If there are changes to the ClearCase
branch, the synch job copies them to RTC as Incoming Changes, where
they have to be MANUALLY accepted into the stream. He wants to
know
if there is a way to AUTOMATICALLY Accept those changes into the
Synchronized stream without performing a MANUAL Accept. Thanks for
any response in advanced.

Susan

Jazz/RTC Support

Great.. thanks for all the help and explanation Geoff! I think I am good to go from here.. but if client has further request, I will open a Jazz.net WI and go from there.

Cheers!

Susan

The main problem is that they apparently are logged in to the RTC
Eclipse client with the cc synchronizer account. That should never be
done. From the CC Connector On-Line Documentation:

"The synchronization process account provides Jazz repository
credentials used by the synchronization process. This account requires a
special class of client access license, and should never be used by a
team member to connect to the repository."

In particular, doing something like manually accepting changes into the
clone workspace (which RTC would have prevented, unless they log in as
the synchronization account) will break the synchronization process.

At this point, the easiest way to proceed is to have the customer create
a new synchronization stream (and make sure they never log in using the
synchronization account). If they want to keep their current
synchronization stream (because it took a long time to do the initial
import), create a jazz.net workitem, and we can walk you through that
process.

Cheers,
Geoff

yisu wrote:

Hi Geoff,

I had a screen share session with the customer.. and I confirmed it is
the clone workspace he has loaded to the pending change view.. and he
has to manually accept changes from the pending change view to
deliver the changes to the CC sync stream.. according to what you
described, was it because he loaded the clone workspace to the
pending change view so he has to manually accept? And if he unload
that workspace, changes will get delivered automatically? please
verify.. thanks.

Susan





gmclemmwrote:
I should have read your original request more carefully ... please
ignore my original response (:-). Corrected response:

The changes from ClearCase are applied directly by the synchronizer
to
the clone workspace, so they wouldn't ever show up as Pending
Changes to
the clone workspace (and a user should never be loading the clone
workspace into your pending changes view anyway ... that's a private

workspace for use just by the synchronizer).

In general, the sync process automatically delivers changes from the

clone workspace to the sync stream unless there are conflicts. So
if
there are no conflicts, then the user should see those changes from

ClearCase automatically appearing in the sync stream when the sync
completes.

To make sure there has been no misunderstanding between you and the

customer, make sure that they clearly identify what workspace they
have
loaded in their Pending Changes view. It is reasonable for them to
load
the Merge Workspace into the Pending Changes view (to confirm there

really are no conflicts).

Cheers,
Geoff

yisu wrote:
Hi Geoff,

Thanks for your response. Could you please elaborate further on
how
to use the RTC build machinery to automate such a process?
Currently, updates sync from ClearCase are pending in the RTC clone
workspace as incoming change set and don't get delivered to the CC
sync stream until client manually accept the changes... How do we
automate this process by using the rtc build machine? Client
understands if there conflicts, they will be placed to the merge
workspace and will not get delivered to the cc sync stream until
they
are resolved. Thanks.

Susan




gmclemmwrote:
You could use the RTC "build" machinery to automatically
schedule such a
process, and use the RTC command line to perform this action. But
note
that this automatic deliver process might fail if parallel changes
have
occurred between RTC and ClearCase, as indicated by the
"conflict"
status that will appear on the sync stream.

Terminological note: you "deliver" changes to a stream,
not accept them
into it.

Cheers,
Geoff

yisu wrote:
Hello,

One of my client asking this:

He has CC sync stream runs every hour, If there are changes in the
RTC
stream it synchs them to the ClearCase branch and checks in a new
version on that branch. If there are changes to the ClearCase
branch, the synch job copies them to RTC as Incoming Changes, where
they have to be MANUALLY accepted into the stream. He wants to
know
if there is a way to AUTOMATICALLY Accept those changes into the
Synchronized stream without performing a MANUAL Accept. Thanks for
any response in advanced.

Susan

Jazz/RTC Support