Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Duplicate
-
None
-
Platform: All, OS: All
Description
I'm using Hudson for monitoring external jobs:
java -jar /path/to/hudson-core.jar "job name" <program arg1 arg2...>
This functionality enables me to have a unified view of many different jobs on
several systems, which is good.
The bad thing is that if my Hudson instance (jetty) is unreachable from the
systems executing the jobs, the jobs are not run!
1) Is there a property defining what to do with the external job if a connection
to Hudson can not be obtained?
2) If not, can I please have such an option. It not a good thing that all the
jobs stop working just because the monitoring tool (Hudson is this case) is
down. Until I get the option, I am not able to use Hudson as a monitoring tool,
it is very important that the jobs run.
Attachments
Issue Links
- duplicates
-
JENKINS-330 External jobs should not fail if server is down
-
- Open
-
As a temporary workaround here is a perl script that executes the job first, then reports to Jenkins. I'm not the author but it works great. It requires perl and curl (but not the Jenkins core jar).
https://gist.github.com/1237898