Starting a JBE build engine for Hudson/Jenkins on CLI fails in RTC 4.0.2, where that same engine worked in 4.0.1
The CMD script we've used to start a JBE Hudson/Jenkins build engine in RTC 4.0.1, fails in RTC 4.0.2.
The return codes explain we cannot use -engineID for a Hudson/Jenkins configured JBE, but we need to use -buildResultUUID.
However there's no explanation, nor example, that describes how the -buildResultUUID should be used in combination with calling JBE from CLI.
Please help!
2 answers
Hi Danny,
I'm sorry about this trail of error codes. The only really important one is the first one you saw ... CRRTC3540E. This one is trying to explain that a Jazz Build Engine is not required for a Hudson/Jenkins build engine, because Hudson/Jenkins *is* the build engine. In other words, your Hudson/Jenkins replaces the need for a JBE.
Here's the online help from 4.0.2
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m2/index.jsp?topic=/com.ibm.team.build.doc/topics/c_hudson_overview.html
I don't believe it has changed much since 4.0.1
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m1/topic/com.ibm.team.build.doc/topics/c_hudson_overview.html
So, try requesting a build without the JBE running on your build engine and you should see your build execute just fine.
Scott
I'm sorry about this trail of error codes. The only really important one is the first one you saw ... CRRTC3540E. This one is trying to explain that a Jazz Build Engine is not required for a Hudson/Jenkins build engine, because Hudson/Jenkins *is* the build engine. In other words, your Hudson/Jenkins replaces the need for a JBE.
Here's the online help from 4.0.2
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m2/index.jsp?topic=/com.ibm.team.build.doc/topics/c_hudson_overview.html
I don't believe it has changed much since 4.0.1
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m1/topic/com.ibm.team.build.doc/topics/c_hudson_overview.html
So, try requesting a build without the JBE running on your build engine and you should see your build execute just fine.
Scott
The -buildId flag for JBE will connect to a particular engine on RTC and start polling that engine for requests. This is not usually what you want for a third party build engine like Hudson because it will remain in a daemon mode, polling that engine. So if you only specify the engineId it will complain if the engine is non-JBE. But if you want the JBE to run something as a one shot, you would want the -buildResultUUID, which assumes that a build has already been created, for example the RTC build that started the Hudson build. The JBE can then use that build result to run. This is useful for executing the JazzSCM participant on the build result by specifying it in the -participants flag for the JBE. This hasn't really changed lately though, so I don't know why this worked before for you.
~Spencer
Comments
Danny Beerens
Jun 10 '13, 8:03 a.m.CRRTC3529W: The execution of Jazz Build Engine completed with a non-zero return code (RC=1). For more details, open the help system and search for CRRTC3529W.
Danny Beerens
Jun 10 '13, 8:06 a.m.Danny Beerens
Jun 10 '13, 8:13 a.m.C:\Program Files (x86)\IBM\IBM Rational Team Concert Buildsystem\buildsystem\buildengine\eclipse>jbe -vm "C:\Program Files (x86)\IBM\TeamConcert\jdk\bin\java"
Danny Beerens
Jun 10 '13, 8:12 a.m.C:\Program Files (x86)\IBM\IBM Rational Team Concert Buildsystem\buildsystem\buildengine\eclipse>jbe -vm "C:\Program Files (x86)\IBM\TeamConcert\jdk\bin\java"