Exiting JBE after completing single build request, RC=1.
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?
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
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.
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.