Team Concert and Build Forge not in sync on build completion status
I have run several RBF builds initiated from RTC via the RTC/RBF integration. These builds have completed, as shown by the RBF console, however, RTC still shows them as in progress. The build results have been recorded in RTC and appear to be complete (along with all the artifact publishing, links, etc). I have restarted both the RBF engine and the JTS. So the question is how do these get out of sync and how do we rectify it? Has anyone else seen this? Is this a known issue that can come up? Note this is happening for one particular build definition, not all of them.
Accepted answer
It is definitely a known issue that can occur. The integration is entirely event driven at the moment so if there is no event to move the build out of its current state, then it will remain in that state. Also the event processing was rocky pre-3.0.1.1. I would say that it is very unlikely to occur in 4.0, but that being said the events only last 20 minutes in BF so if it is stuck for longer than that, the only recourse is to cancel the RTC build. We have also seen problems with sharing BF user ids between RTC instances that can cause synchronization problems.
~Spencer
2 other answers
We have the same issue overhere with RTC 4 and buildforge 7.1.3.3.
@Spencer : you said it is a know issue. Is there any defect we can follow ?
@Spencer : you said it is a know issue. Is there any defect we can follow ?
Julien, Was your issue resolved? We are experiencing similar issues after RTC upgrade
Well, as far as I know the only integration between Buildforge and RTC is thru the JBE adaptor. (which simply launch the jbe on request). To resume the situation and give some updates : Everything was working fine when RTC was 3.x as soon as we updated to 4.0, ssl connection did not work anymore and so much more ... Now that we moved to 4.0 : - Buildforge build engine are always marked with "warning - The build engine process may not be running" : if I do a "Test connection, test ends up succesfully). - When I kick off a build from RTC (right click - request a build then submit) I get a popup saying that my build do not appear to be processing request BUT, if I do the same request and update the Build Engine property (in the request pop up) with the buildforge build engine, then the build is kicked off ... (Looks like there is something broken between builds engine and build definition). - Also when builds run into buildforge I get no progess in RTC (the build status is always "no progress information" and never ends - even if the build is finished on the buildforge side ...) so I have to check into buildforge that my build is finished then do an "Abandon" in RTC..
Well, as far as I know the only integration between Buildforge and RTC is thru the JBE adaptor. (which simply launch the jbe on request). To resume the situation and give some updates : Everything was working fine when RTC was 3.x as soon as we updated to 4.0, ssl connection did not work anymore and so much more ... Now that we moved to 4.0 : - Buildforge build engine are always marked with "warning - The build engine process may not be running" : if I do a "Test connection, test ends up succesfully). - When I kick off a build from RTC (right click - request a build then submit) I get a popup saying that my build do not appear to be processing request BUT, if I do the same request and update the Build Engine property (in the request pop up) with the buildforge build engine, then the build is kicked off ... (Looks like there is something broken between builds engine and build definition). - Also when builds run into buildforge I get no progess in RTC (the build status is always "no progress information" and never ends - even if the build is finished on the buildforge side ...) so I have to check into buildforge that my build is finished then do an "Abandon" in RTC..
