-
Bug
-
Resolution: Won't Fix
-
Major
I've noticed a problem with the Naginator plugin and archiving.
My jobs has two post-build actions, in the following order:
(1) "Retry build after failure" (Naginator), with "Only rerun build if regular expression is found in output" selected.
(2) "Archive the artifacts"
If my build ends in failure (but the output does not match the naginator regex), then the job hangs. The console log shows:
Build step 'Execute shell' marked build as failure Archiving artifacts
And then it takes a LONG time before the job actually ends (or else it never ends at all).
What is worse is that it you look at the web page for the job, the job shows as finished. However, if you look at main web page, the job shows as still running, and using an executor.
[JENKINS-19071] Naginator plugin causes archiving to hang if the build failed
Tomer Galun
added a comment - Right now on hold. If you can reproduce this issue with the newest version and it affects you - reopen
Tomer Galun
added a comment - Right now on hold. If you can reproduce this issue with the newest version and it affects you - reopen 
Matthew Webber
added a comment - I'm not currently using Naginator, so I can't report check whether the problem is stil there. Sorry.
Matthew Webber
added a comment - I'm not currently using Naginator, so I can't report check whether the problem is stil there. Sorry. 
I tried swapping the order of the psot-build actions (so archive first, and Naginator second), but the result was the same - the job hangs during archiving.
My details: this was with Jenkins 1.526, but I have been noticing the problem on and off for some months. The jenkins master is a Linux RHEL6 machine, the job ran on a Linux RHEL6 slave.