second ClearCase Synchroniser want's to create an evil twin
Hello,
I was wondering if someone already came across this situation and knowos how to deal with it. We build up a CC-RTC-Round-Synchronisation. One clearcase synchroniser is set up to bring changes from CC to RTC. Another clearcase synchroniser brings changes from RTC to CC. On either sides changes of the code may be introduced, integration and build is going to happen on RTC. The builded (and tested) sources are then synced back to (another branch in) CC through the second synchroniser. When a new file is created in CC and then brought over to RTC through the first synchroniser the second one will bring it back to clearcase after build and test took place. During the back sync the evil-twin-trigger fires and prevents from creating a new element in CC which indeed is or should be recognised as the same element that has already been synced forward before, but in the other branch. So what is the approach to handle new introduced files in such a scenario? Thanks in advance for your thoughts, michl |
3 answers
Ralph Schoon (63.5k●3●36●46)
| answered Jul 23 '15, 4:57 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I have never heard someone using two synchronizers. The typical scenario is using one. I can only imagine that using two synchronizers somehow introduces this problem.
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 23 '15, 1:55 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
When you say you "build up a CC-RTC-Round-Synchronisation", do you mean you implemented your own synchronizer, or that you are using the CC-Synchronizer that is part of the RTC product? If it is the RTC CC-Synchronizer, then that will not create evil twins ... it will re-use the appropriate existing ClearCase element, even if the element was created by a different synchronization stream. If you believe that it is creating evil twins, then you should work with RTC Support to find out why.
On the other hand, if it is a synchronizer that you implemented yourself, then it would be up to you to modify your synchronizer implementation to avoid creating evil twins. |
|
Hello Geoff, hello Ralph,
thank you for your answers. Actually we are using the clearcase-RTC synchronizer as provided from IBM. I also thought that the ClearCase elements ID is used and that a clearly defined association is made between elements in RTC and elements in ClearCase. But elements that were created in on branch in CC and are then synchronised with RTC, propagated to another stream and then synched back to ClearCase makes the synchronizer fail with the following error: Error: duplicate name '...' found in directory version ...@@/main/team/4 cleartool: Warning: Trigger "pre_lnname_evil_twin" has refused to let lnname proceed. Interactive triggers are not supported in the Web interface. If the trigger was interactive, it may have ailed for that reason. cleartool: Error: unable to create link: "M:\Do_NOT_USE_..." Maybe it also has to do with some specific configurations at this installation. The short term approach is to reduce the set up to one synchroniser but we may run into this very same situation again as soon as we start synchronizing different version-branches with RTC. So contacting Rational Support seems a good idea ,,, Thanks again, any thoughts are highly welcome.-) best michl |
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.