It's all about the answers!

Ask a question

Exiting JBE after completing single build request, RC=1.


Xue Yan (11) | asked Aug 18 '10, 12:12 a.m.
Hi,
I got this problem and can't find a way to handle it.


287 8/18/10 9:44 PM EXEC 2010-08-18 19:44:37 Yes: Always build a user initiated request.
288 8/18/10 9:44 PM EXEC 2010-08-18 19:44:37 Invoking pre-build participant "com.ibm.team.build.jazzscm"
289 8/18/10 9:44 PM EXEC 2010-08-18 19:44:37 Exiting JBE after completing single build request, RC=1.

I've got an incoming change set in the pending change view.
But how can I find out why JBE runed failed?

3 answers



permanent link
Nick Edgar (6.5k711) | answered Aug 19 '10, 4:52 p.m.
JAZZ DEVELOPER
What command line are you using to invoke JBE? Are you using JBE by itself, or in conjunction with the Build Forge integration?

permanent link
Julien Delgoulet (6) | answered Aug 08 '11, 4:05 a.m.
What command line are you using to invoke JBE? Are you using JBE by itself, or in conjunction with the Build Forge integration?


I do have the exact same "failure" and need to debug but no info at all ...
I personnaly use RTC 3.0.1 with buildforge and the jazzJBE adaptor.

permanent link
Nick Edgar (6.5k711) | answered Aug 08 '11, 10:12 a.m.
JAZZ DEVELOPER
When JBE is used with Build Forge, i.e. using the JazzJBE adapter (or equivalent), the "Exiting JBE after completing single build request" message is normal, since that adapter invokes JBE in a "one-off, single given build" mode, as opposed to its normal polling mode.

But the "RC=1" does indicate an error. Normally it would write the error to the build log and associate it with the build result. Can you check the build result? If it's not there, there may have been an error in publishing it, so check for a build-<timestamp>.log file in the current working directory in effect when JBE was launched.

Your answer


Register or to post your answer.