We have an issues while managing a synchronize for wrong data delivery to stream
- 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
Comments
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>
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.