I have a Hudson server that runs maven 3 jobs to compile Java code. In one case, a particular job assembly log shows that compilation and unit tests were successful, and the build was completed in a successful state, and another chain work was called up, all of which indicated that Hudson considered this job to be successful. The log displays:
20:44:11 [INFO] BUILD SUCCESS
20:44:11 [INFO] ------------------------------------------------------------------------
20:44:11 [INFO] Total time: 1:35:43.774s
20:44:11 [INFO] Finished at: Mon Mar 24 20:44:11 CDT 2014
20:44:40 [INFO] Final Memory: 51M/495M
20:44:40 [INFO] ------------------------------------------------------------------------
20:44:42 channel stopped
20:44:42 [locks-and-latches] Releasing all the locks
20:44:42 [locks-and-latches] All the locks released
20:44:43 Archiving artifacts
20:45:33 Updating JIRA-1234
20:45:33 Description set: 1.23.567
20:45:33 Labelling Build in Perforce using ${BUILD_TAG}
20:45:33 [jobname] $ /usr/local/bin/p4 -s label -i
20:45:33 Label 'hudson-jobname-45' successfully generated.
20:45:33 [DEBUG] Skipping watched dependency update; build not configured with trigger: jobname #45
20:45:33 Finished: SUCCESS
However, a red ball is displayed on Hudson's quest page , and this quest appears as "Last failed build (# 45)" on the quest page. When I look at the hudson @hudson file: ~ hudson / jobs / jobname / builds / 45 / build.xml, there is a line that says
<result>FAILURE</result>
, ,
<result>SUCCESS</result>
, . , .
, . , Hudson
ps -ef | grep hudson.war
, . , "Took 0 ms", " : 1: 35: 43,774s". . 2.2.1 "CentOS release 5.4 (Final)".
: