It's all about the answers!

Ask a question

ClearCase Synchronizer workflow


Geoffrey Clemm (30.1k33035) | asked Aug 12 '10, 3:19 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I got the following question via email, and thought I'd answer it in the
forum:

-----------
- When sync happens ,
1 - how the changes are accepted in merge/clone workspace
2 - does the changes automatically checked in Clone workspace
3 - How those changes flow from ccsync stream to main project stream
4 - when changes happen to RTC stream, how those changes flow back
to ccsync stream
5 - How teams gets communicated with new sync changes
-----------

General comment: You shouldn't be thinking about the CLONE workspace,
other than knowing that it contains a "clone" of the ClearCase stream.
The only time you are aware of it at all is when the synchronization
reports a "conflict". Then, you accept changes from the CLONE workspace
and the sync stream into the merge workspace in order to perform the merges.

1 - Changes are accepted into the merge workspace explicitly by the
owner of the merge workspace.

2 - No quite sure how to parse this question, but all change flow into
the CLONE workspace automatically by the sync algorithm. Humans never
make changes to that workspace (which is why it is owned by the "CC
Synchronizer Account", and not be a normal user.

3 - Flowing changes from the ccsync stream to the main project stream is
done using standard RTC mechanisms. Note that the CC Synchronizer has
no knowledge of what stream is the main project stream (or even if there
is one).

4 - There are two streams that the synchronizer keeps in sync ... one in
ClearCase (let's call that the CC sync stream) and one in RTC (let's
call that the RTC sync stream). So assuming you are asking "when
changes happen to the RTC sync stream, how do those changes flow back to
the CC sync stream", then that is just part of what the synchronizer
does ... a sync request brings changes from the CC sync stream, merges
them into the Jazz sync stream, and then sending the results of that
merge back to CC.

5 - A team finds out about changes to the RTC sync stream just by the
usual RTC mechanisms (it's just a normal RTC stream), e.g., have in your
Pending Changes a personal workspace whose flow target is the RTC sync
stream. The only time special processing is needed is when there is a
sync conflict ... in that case, you find out by the standard "build
result notification" mechanisms (the synchronizer just uses the RTC
Build engine).

Cheers,
Geoff

2 answers



permanent link
Madhu Gaur (161) | answered Aug 15 '10, 2:10 a.m.
I got the following question via email, and thought I'd answer it in the
forum:

-----------
- When sync happens ,
1 - how the changes are accepted in merge/clone workspace
2 - does the changes automatically checked in Clone workspace
3 - How those changes flow from ccsync stream to main project stream
4 - when changes happen to RTC stream, how those changes flow back
to ccsync stream
5 - How teams gets communicated with new sync changes
-----------

General comment: You shouldn't be thinking about the CLONE workspace,
other than knowing that it contains a "clone" of the ClearCase stream.
The only time you are aware of it at all is when the synchronization
reports a "conflict". Then, you accept changes from the CLONE workspace
and the sync stream into the merge workspace in order to perform the merges.

1 - Changes are accepted into the merge workspace explicitly by the
owner of the merge workspace.

2 - No quite sure how to parse this question, but all change flow into
the CLONE workspace automatically by the sync algorithm. Humans never
make changes to that workspace (which is why it is owned by the "CC
Synchronizer Account", and not be a normal user.

3 - Flowing changes from the ccsync stream to the main project stream is
done using standard RTC mechanisms. Note that the CC Synchronizer has
no knowledge of what stream is the main project stream (or even if there
is one).

4 - There are two streams that the synchronizer keeps in sync ... one in
ClearCase (let's call that the CC sync stream) and one in RTC (let's
call that the RTC sync stream). So assuming you are asking "when
changes happen to the RTC sync stream, how do those changes flow back to
the CC sync stream", then that is just part of what the synchronizer
does ... a sync request brings changes from the CC sync stream, merges
them into the Jazz sync stream, and then sending the results of that
merge back to CC.

5 - A team finds out about changes to the RTC sync stream just by the
usual RTC mechanisms (it's just a normal RTC stream), e.g., have in your
Pending Changes a personal workspace whose flow target is the RTC sync
stream. The only time special processing is needed is when there is a
sync conflict ... in that case, you find out by the standard "build
result notification" mechanisms (the synchronizer just uses the RTC
Build engine).

Cheers,
Geoff




Thanks Geoff, I understand the flow better now. Somehow when sync happens it does not accept the changes automatically so I have to manually accept them. What am I doing wrong ?
I have been using ccsync id to perform the task. Logged in to RTC as this user as well as the workspace is owned by ccsync user

permanent link
Geoffrey Clemm (30.1k33035) | answered Aug 15 '10, 9:17 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I'll use Madhu's note as an excuse for some general guidance.

General guidance: Because the CC Synchronizer is setting up an automated
process for communicating between the RTC SCM system and ClearCase via
the RTC Build system, unless you are intimately familiar with all three
of these systems (including setting up user accounts and permissions),
you will want to carefully read the on-line CC Synchronizer
documentation *before* trying to create your first sync stream.

For example, in the "Basic Concepts" section, it says:

ClearCase Synchronization Jazz user:
Jazz user account that provides credentials to the synchronization
process so that it can access your repository and team area; requires
a special class of client access license; should never be used by a
team member to connect to the repository

If you do log on as this user, you have permissions to do various
advanced things that can disrupt the sync process (think of it as
"super-user for the synchronizer"). Until you are a very advanced user,
you are likely as super user to mess things up (so don't do that :-).

So you'll want to do the following:
- delete whatever synchronized streams you've created (there's a
"delete" operation available in the Synchronized ClearCase Streams view)
- read the on-line documentation
- create new sync-streams, following the "how to" guidance in the
on-line documentation

And of course, always feel free to post to this forum if you have any
trouble.

Cheers,
Geoff

On 8/15/2010 2:22 AM, madhug wrote:

Somehow when sync
happens it does not accept the changes automatically so I have to
manually accept them. What am I doing wrong ?
I have been using ccsync id to perform the task. Logged in to RTC as
this user as well as the workspace is owned by ccsync user

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.