It's all about the answers!

Ask a question

Need help on ClearCase synchronization in RTC


0
1
Penchala suman (461425) | asked Oct 20 '14, 11:18 a.m.
 We are doing a sync from ClearCase (Stream A) to RTC (Stream B) and we have created another stream based on Stream A called as Stream C, development in RTC on Stream C.

Here is the details what we do actually.

 

1.       There is some development in Stream A ClearCase side and will do every day sync to RTC, so all changes will reflect to Stream B in RTC.

2.       Once all changes are in to RTC Stream B and will accept all changes from Stream B to Stream C (only one way B to C)

Note: There is no development in Stream B and our development will be in Stream C in RTC

The problem is:

1.       One of our Developer by mistake he deliver changes from Stream C to Stream B (we never do this)  and then sync is bring all change from Stream B to Stream A.

2.       So we have cleaned all changes are come from Stream B to Stream A in ClearCase (removed those versions).

3.       But still we have changes in stream B  those wrong delivery. There was some issue to remove changes from stream B of stream C changes. Because when we remove those changes while accepting changes from Stream B to Stream C it will over write stream C changes by Stream B.

4.       One good thing is when we do a sync changes are coming from CC to RTC, removed version in ClearCase are not reflecting again even through the changes are in Stream B.

 

We are not sure what do exactly now to resolve this issue, any suggestions please.

One answer



permanent link
Geoffrey Clemm (30.1k33035) | answered Oct 21 '14, 1:34 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Did you try:
- accept Stream B into a workspace,
- discard from that workspace the change sets that came from Stream C
- use the "replace" operation to update stream B with the configuration of the workspace.
Then there should be no incoming changes from stream B to Stream C.

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.