-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Platform: All, OS: All
We installed and configured the buildtimeout plugin.
We now found it working, our builder exceeded the time set and got aborted.
The aborted state results in a gray icon and nothing more.
At least I expect a mail that the build got aborted. But I think it is a failure
of the build.
We use this buildtimeout to prevent a hanging build. We normally have a build of
4 minutes so I configured the buildtimeout on 10 minutes. Now due to a
implementation issue our build exceeded the 10 and we expected it to break.
- duplicates
-
JENKINS-1288 Build-timeout-plugin should mark job as "failure" instead of "aborted"
-
- Closed
-
With a small change in hudson.tasks.MailSender this can be fixed:
protected MimeMessage getMail(AbstractBuild build, BuildListener listener)
{ return createFailureMail(build, listener); }throws MessagingException, InterruptedException {
if (build.getResult() == Result.FAILURE)
//NEW PART FOR ABORTED
{ MimeMessage msg = createFailureMail(build, listener); msg.setSubject(getSubject(build, "Build aborted in Hudson: "),"UTF-8"); }if (build.getResult() == Result.ABORTED)
if (build.getResult() == Result.UNSTABLE) {
{ if (prev.getResult() == Result.SUCCESS) return createUnstableMail(build, listener); }AbstractBuild prev = build.getPreviousBuild();
if (!dontNotifyEveryUnstableBuild)
return createUnstableMail(build, listener);
if (prev != null)
}
if (build.getResult() == Result.SUCCESS) {
{ //ABORTED CHECK ADDED if (prev.getResult() == Result.FAILURE || prev.getResult() == Result.ABORTED) return createBackToNormalMail(build, "normal", listener); if (prev.getResult() == Result.UNSTABLE) return createBackToNormalMail(build, "stable", listener); }B prev = build.getPreviousBuild();
if (prev != null)
}
return null;
}
IMO 'Aborted' is an exceptional state and mails should be sent on this state.