-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Debian Lenny, Jenkins ver. 1.404 and build-timeout ver. 1.7
I just installed the build-timeout plugin and it's mostly working, but
even with the "Fail the build" setting checked, my builds are still
being marked as "aborted":
For example, here is the tail of the console output:
{{
[...]
Build timed out (after 3 minutes). Marking the build as failed.
Terminated
+++ vncserver -kill beast:3 -clean
Killing Xtightvnc process ID 12328
+++ exit
Finished: ABORTED
}}
Note that it says it will fail the build, but then it is aborted and
the status of the build is set to aborted, not failed. Bonus pain:
Of course no email goes out.
This is with Jenkins ver. 1.404 and build-timeout ver. 1.7.
- is related to
-
JENKINS-9548 Build Timeout plugin does not mark build as failed even when option is selected
-
- Resolved
-
[JENKINS-9203] timer expires, and build is halted, but build is not marked as failed
Description |
Original:
I just installed the build-timeout plugin and it's mostly working, but even with the "Fail the build" setting checked, my builds are still being marked as "aborted": For example, here is the tail of the console output: {{ [...] Build timed out (after 3 minutes). Marking the build as failed. Terminated +++ vncserver -kill beast:3 -clean Killing Xtightvnc process ID 12328 +++ exit Finished: ABORTED }} Note that it says it will fail the build, but then it is aborted and the status of the build is set to aborted, not failed. Bonus pain: Of course no email goes out. This is with Jenkins ver. 1.401 and build-timeout ver. 1.7. |
New:
I just installed the build-timeout plugin and it's mostly working, but even with the "Fail the build" setting checked, my builds are still being marked as "aborted": For example, here is the tail of the console output: {{ [...] Build timed out (after 3 minutes). Marking the build as failed. Terminated +++ vncserver -kill beast:3 -clean Killing Xtightvnc process ID 12328 +++ exit Finished: ABORTED }} Note that it says it will fail the build, but then it is aborted and the status of the build is set to aborted, not failed. Bonus pain: Of course no email goes out. This is with Jenkins ver. 1.404 and build-timeout ver. 1.7. |
Environment | Original: Debian Lenny | New: Debian Lenny, Jenkins ver. 1.404 and build-timeout ver. 1.7 |
Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
And also, if a build is configured to be triggered when the "timed out" build is failed, the build is not triggered.
Our Configuration :
Hudson Master SUN OS 10
Java 1.6.0.18
Jenkins 1.404
Build Timeout 1.7
Hudson Slave :
Linux RH5
java 1.6.0_21-b06
A Test done with a Hudson 1.395 and BuildTimeOut 1.6 shows that it was OK with these couple of version.