JBE Error in Hudon Build
I have a Build definition that always returns the following error as a result:
2012-10-25 15:46:49 [Jazz build engine] Invoking pre-build participant "com.ibm.team.build.jazzscm" 2012-10-25 15:46:51 [Jazz build engine] Exiting JBE after completing single build request, RC=1. 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.
What bothers me, is I have a similar build definition that does precisely the same thing, except loads a different component, and it always seems to work.
My build definition is a Hudson Build using Jazz Source Control, It selects a single component from a workspace and
then the hudson build calls jbe passing repositoryAddress, buildRequestUUID, buildLabel, and buildEngineID as parameters along with
the BuildUser username and password, and everytime it returns this error. Precisely the same build definition loading
different components works. There is nothing wrong with this component, I can load it in RTC, build it with the makefile that exists in the component,
etc and have no issues, but running JBE it seems to give this error constantly, however I have on rare occasions seen it work (My Hudson build has a few
random successes).
I'd be willing to run a Teamviewer remote desktop session to demonstrate if necessary to try to fix/resolve/figure out this issue
Thanks!
Chris
2 answers
Comments
Martina, can you provide details here on what the problem was, so others can benefit if they hit this? Or was it the same case as what Chris reported?
I was doing some tests on Linux and AIX and the source code didn't get loaded where I was looking for it. This is with Build Forge integration. I had the exact same BF log as posted above. This post made me look at the extra log in RTC. The issue in one case was that my test stream has 2 components that are very similar and I needed to select "load components as directories".
Thanks, Martina.
Comments
Nick,
Its always is the same (I've starred out passwords):
Started by user anonymous [workspace] $ /bin/sh -xe /tmp/hudson2502439142108475678.sh + /opt/IBM/buildsystem/buildengine/eclipse/jbe -repository https://jazz.aeroflex.com:9443/jazz/ -userId BuildUser -pass * -engineID 7200_Hudson_Engine -buildResultUUID _JqnqMB7lEeKfid16ofHALg -participants com.ibm.team.build.jazzscm -noComplete -verbose Supplied arguments: -repository https://jazz.aeroflex.com:9443/jazz/ -userId BuildUser -pass * -engineID 7200_Hudson_Engine -buildResultUUID _JqnqMB7lEeKfid16ofHALg -participants com.ibm.team.build.jazzscm -noComplete -verbose Java Version: JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr11-20120801_118201 (JIT enabled, AOT enabled) J9VM - 20120801_118201 JIT - r9_20120608_24176ifx1 GC - 20120516_AA Engine Bundle Version: com.ibm.team.build.engine, 3.0.100.v20120430_0235 2012-10-25 15:46:43 [Jazz build engine] Searching for buildResultUUID=_JqnqMB7lEeKfid16ofHALg 2012-10-25 15:46:43 [Jazz build engine] The -noComplete argument was specified. The build result will not be completed by JBE. 2012-10-25 15:46:43 [Jazz build engine] Building only the specified participants: "[com.ibm.team.build.jazzscm]" 2012-10-25 15:46:45 [Jazz build engine] Not using a proxy to reach https://jazz.aeroflex.com:9443/jazz/ Oct 25, 2012 3:46:46 PM org.apache.commons.httpclient.HttpMethodDirector isAuthenticationNeeded INFO: Authentication requested but doAuthentication is disabled 2012-10-25 15:46:48 [Jazz build engine] Searching for build request... 2012-10-25 15:46:49 [Jazz build engine] Found a user request for build definition "7200_Kernel_build". 2012-10-25 15:46:49 [Jazz build engine] Build participant "com.ibm.team.build.cmdline" was not specified on -participants list. 2012-10-25 15:46:49 [Jazz build engine] Build participant "com.ibm.team.build.ant" was not specified on -participants list. 2012-10-25 15:46:49 [Jazz build engine] Build participant "com.ibm.team.build.maven" was not specified on -participants list. 2012-10-25 15:46:49 [Jazz build engine] Build participant "com.ibm.team.build.junit.publishing" was not specified on -participants list. 2012-10-25 15:46:49 [Jazz build engine] Build participant "com.ibm.team.build.jdt.publishing" was not specified on -participants list. 2012-10-25 15:46:49 [Jazz build engine] Build participant "com.ibm.team.build.msbuild" was not specified on -participants list. 2012-10-25 15:46:49 [Jazz build engine] Build participant "com.ibm.team.build.mstest.config" was not specified on -participants list. 2012-10-25 15:46:49 [Jazz build engine] Build participant "com.ibm.team.build.nunit.config" was not specified on -participants list. 2012-10-25 15:46:49 [Jazz build engine] Build participant "com.ibm.team.build.autoDeliver" was not specified on -participants list. 2012-10-25 15:46:49 [Jazz build engine] Should build occur? 2012-10-25 15:46:49 [Jazz build engine] Yes: Always build a user initiated request. 2012-10-25 15:46:49 [Jazz build engine] Invoking pre-build participant "com.ibm.team.build.jazzscm" 2012-10-25 15:46:51 [Jazz build engine] Exiting JBE after completing single build request, RC=1. 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.
1 vote
That is the JBE console output (which will appear in the Hudson/Jenkins log). I meant is there any log published to the RTC build result?
Nick I misunderstood. I did find the build result log in the RTC Build Results, and it revealed something very interesting that seems to have been the problem. I thought i'd scoped everything, but somehow there were a set of components that were scoped to get files from two different streams. This was causing the JBE to fail. I went into the build workspace, ensured all components were correctly scoped, and it started to work correctly.
So moral of the story: Make sure your components are correctly scoped to only flow from one stream.
Good to hear. Unlike regular repository workspaces for individuals, the build one accepts from all targets it has. This can be useful, but in that case you need to scope the flows to avoid collisions between components. Remember that each build definition should have a dedicated build workspace, and that it shouldn't be used in other ways, e.g. as a developer workspace.