It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,872

question asked: Sep 25 '14, 6:57 a.m.
question was seen: 2,378 times
last updated: Sep 26 '14, 10:19 a.m.

Related questions

We have an issues while managing a synchronize for wrong data delivery to stream

0
Penchala suman (46●14●25) | asked Sep 25 '14, 6:57 a.m.
 -          Actually we are running the sync from CC to RTC for 3.15 stream (all users are working on CC side)

-          They have created 3.30 stream from 3.15 baseline.

-          Whenever they got new changes on 3.15 stream and they will accept from 3.15 to 3.30 (one way only)

-          But, one of the developer by mistake accepted the changes from 3.30 to 3.15 stream (other way)

-          After that we have synchronized the 3.15 stream, all 3.30 stream data went ClearCase on 3.15,  because of that wrong data, build are failed. So we have removed all CC version was created by synchronizer.

-          Now ClearCase side source code looks fine, but in RTC side still some of the 3.30 changes are in 3.15 stream.

-          We want to resolve this issue without impact to existing setup and After fixing the issue we can able to merge changes from 3.15 to 3.30 without any impact of file difference.

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Tim Mok (6.6k●3●8) | answered Sep 25 '14, 10:48 a.m.
JAZZ DEVELOPER
You should disable the synchronizer for now to make it easier to fix your 3.15 stream. If you've created baselines or snapshots in your 3.15 stream, you should be able to replace your 3.15 stream with a known good configuration prior to the 3.30 to 3.15 delivery.

If there is an easy way for you to identify changes that belong to 3.30 (eg. associated work items planned for 3.30 or some other way), you can discard them from a repository workspace based on the 3.15 stream. When it is in the correct configuration, replace the components of the 3.15 stream with the components from the fixed repository workspace.
Comments
Penchala suman commented Sep 26 '14, 10:15 a.m.

 I've replaced the component after we fixed wrong activities, initially it shows fine and it removed wrong data. But after the sync it came back previous history baseline has fixed those file. Seems to be older baseline has those changes and not able to hide them. But luckily now sync is working one way from CC to RTC. Even through it is not to sync existing configuration. How can we proceed further to fix the issue.

How to remove older baseline history on my stream. <o:p> </o:p>

Tim Mok commented Sep 26 '14, 10:19 a.m.
JAZZ DEVELOPER

As long as your current configuration is good, there's no need to clean up the older baselines. Baselines are immutable so that mistake will always be preserved. It's irrelevant whether the baselines are in the stream's baseline history or not. What matters is the change sets that you didn't want are no longer in the stream.

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.