Anomalies with RTC/BF configuration and interoperation
RTC server : 2.0.0.2 iFix 2 (I20100331-2220)
Jazz Build tool kit from same Build forge server plugin: 7.1.1.4020139 I have created a BF project and connected it to an RTC build definition. Unless I start the jbe the job will never start. Having the jbe always 'succeeds' with this:
The jazz server mutters this as it is starting up.
I've tried to read through https://jazz.net/wiki/bin/view/Main/RationalBuildForge/IntegrationWithRTC and think I'm close. I'm particularly puzzled about the "no engine participant" message. I did find a post about that, but for me it leads nowhere. |
12 answers
Ive got the same problem.
After stopping the jbe, Ive got the message "The build engine process may not be running." and with that again no job starts. |
When using a "Rational Build Forge" build definition, you shouldn't use "JBE" with it. This build definition will connect to Build Forge to start Jobs and look for Job events (started, stopped, etc). To get the server-side connector (listener) installed, you need to unzip the BuildForgeConnectorServer.zip from the Build Forge webroot\public\rtc2-server update site (copy it over to the RTC server directory and unzip it there. Upon restart of RTC, this "scheduled task" will begin to listen for BF jobs in the queue. The only time JBE is involved with a Build Forge definition is when it's used on the BF project to invoke the Jazz SCM participant, but this is an RTC 3.0 feature. Let me know if this does not help and you have more questions.
Regards, Pete |
When using a "Rational Build Forge" build definition, you shouldn't use "JBE" with it. This build definition will connect to Build Forge to start Jobs and look for Job events (started, stopped, etc). To get the server-side connector (listener) installed, you need to unzip the BuildForgeConnectorServer.zip from the Build Forge webroot\public\rtc2-server update site (copy it over to the RTC server directory and unzip it there. Upon restart of RTC, this "scheduled task" will begin to listen for BF jobs in the queue. The only time JBE is involved with a Build Forge definition is when it's used on the BF project to invoke the Jazz SCM participant, but this is an RTC 3.0 feature. Let me know if this does not help and you have more questions. I pointed out the Build Forge connector characteristics in my original post. When I let the RTC build definition use the 'default' build engine it never starts. In the RTC server configuration (advanced) I do see the Build Forge settings for the user id: IBM Rational Build Forge Connector Service Edit com.ibm.rational.buildforge.team.service.BuildForgeBuildLoopScheduledTask Property Current Value Build Forge Connector Build Loop Task Contributor Id rtcbuild Default Value ADMIN Property Build Forge Connector Build Loop Task Fixed Delay(seconds) Current Value 90 Default Value 15 Edit com.ibm.rational.buildforge.team.service.BuildForgeEventPollerScheduledTask Property Current Value Build Forge Connector Event Poller Task Contributor Id rtcbuild Default Value ADMIN Property Build Forge Connector Event Poller Task Fixed Delay(seconds) Current Value 90 Default Value 15 |
|
This trace is going to the tomcat catalina.out file:
|
|
Is the user "rtcbuild" defined for all of your Project Areas where build defs are defined? It appears to be a fetchItem missing for the runAS user. Can you try setting it back to ADMIN and giving Everyone all of the BUILD permissions for the time being?
Regards, Pete |
Is the user "rtcbuild" defined for all of your Project Areas where build defs are defined? It appears to be a fetchItem missing for the runAS user. Can you try setting it back to ADMIN and giving Everyone all of the BUILD permissions for the time being? No. The reason being all our RTC is ldap. But I'll give your suggestion a whirl. |
|
Getting closer. I see the RTC build forge build engine go to Busy
and the rtcbuild ID configured into the build definition is logging into Build Forge. But getting another exception:
I've gone through the permissions for the project, environment, adapter link and the rtcbuild in build forge ought to have permission. |
Getting closer. I see the RTC build forge build engine go to Busy Good, sounds like the task is listening now. Do you see any errors in the tomcat/logs/catalina.log on the Build Forge side? Can you try kicking off a build for this project directly from BF? Regards, Pete |
|
Starting the project from Build Forge side works and updates RTC with various artifacts ( a link to the build result, and the build log).
I'll check the tomcat logs on the Build forge server. Getting closer. I see the RTC build forge build engine go to Busy Good, sounds like the task is listening now. Do you see any errors in the tomcat/logs/catalina.log on the Build Forge side? Can you try kicking off a build for this project directly from BF? Regards, Pete |
|
So close now.
Starting build from RTC side still gets hung up. In the Build Forge tomcat log:
I double checked the BF project environment. It has the workspace and the buildResultUuid, but it never seems to get set. Latest attempt RTC exception:
Build Forge exception:
|
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.