|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Well, generally a vanilla Jenkins job may not work properly (and don't notify about it) due to the following reasons (I'm referring to bash here):
1) The script isn't catching all errors. Jenkins launches the scripts with "-xe" options by default. A more robust way is "-xeu -o pipefail". This is trivial to do.
2) Not all commands return correct exit code on failure. "Log parser" plugin often helps here.
3) The node isn't available at the time, as described in this issue. Right now I'm using https://wiki.jenkins-ci.org/display/JENKINS/Monitor+and+Restart+Offline+Slaves, but it's not enough.
4) Some step hangs, so the build is never completed and the next one is in queue forever. Fortunately, there's a "Build timeout" plugin for that.
I think that's all.