It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,790
×5,999
×101
×76

question asked: Oct 25 '12, 4:54 p.m.
question was seen: 7,610 times
last updated: Apr 22 '13, 9:25 a.m.

Related questions

FAQ - How this Forum works

JBE Error in Hudon Build

1
Chris Fagyal (46●2●10●9) | asked Oct 25 '12, 4:54 p.m. 
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

Most liked answers|Newest answers ↑|Oldest answers

0
permanent link
Martina Riedel (203●2●33●41) | answered Apr 19 '13, 8:34 p.m.
Looking at the "additional" / "somewhat unexpected" build result log in RTC helped me find what I had wrong!
Comments
Nick Edgar commented Apr 20 '13, 8:53 a.m. | edited Apr 20 '13, 8:53 a.m.
JAZZ DEVELOPER

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?

Martina Riedel commented Apr 20 '13, 9:07 a.m. | edited Apr 20 '13, 9:08 a.m.

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".

On the AIX the jbe.sh that we have had a hard coded cd that made the code being loaded into the buildtoolkit path and not under BF root.
In both cases the messages in the RTC log is what I needed to see in order to fix things

Hth

Nick Edgar commented Apr 22 '13, 9:25 a.m.
JAZZ DEVELOPER

Thanks, Martina. 
2
permanent link
Nick Edgar (6.5k●7●11) | answered Oct 29 '12, 11:54 p.m.
JAZZ DEVELOPER
Hi Chris, was there anything in the build's log?  If it wasn't able to get published, check the JBE working directory for a file with name: build-(some number).log

Comments
1
Chris Fagyal commented Oct 30 '12, 9:21 a.m. | edited Oct 30 '12, 1:44 p.m.

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.

Nick Edgar commented Oct 30 '12, 1:44 p.m. | edited Oct 30 '12, 1:44 p.m.
JAZZ DEVELOPER

 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?

Chris Fagyal commented Oct 30 '12, 2:32 p.m. | edited Oct 31 '12, 11:18 a.m.

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.

Nick Edgar commented Oct 31 '12, 11:20 a.m.
JAZZ DEVELOPER

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.


If this works for you now, please mark the answer above as accepted. 

Your answer

Register or to post 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.