[JENKINS-330] External jobs should not fail if server is down - Jenkins Jira

XML

Word

Printable

Details

Type: Improvement
Status: Open (View Workflow)
Priority: Minor
Resolution: Unresolved
Component/s: external-monitor-job-plugin
Labels:
None
Environment:
Platform: All, OS: All

Similar Issues:

Show

Description

Hudson jobs that are run manually from the command line should not fail simply
because the server running at $HUDSON_HOME isn't responding.

Attachments

Issue Links

is duplicated by

JENKINS-1677 External job will not be executed of connection to Hudson can't be obtained.

Resolved

Activity

Ascending order - Click to sort in descending order

ryan_shoemaker added a comment - 2007-02-26 11:03

The current code simply dumps a "java.net.ConnectException: Connection timed out
" stacktrace if it is unable to contact the Hudson server and terminates without
running the underlying job. This should be improved by printing a warning
message explaining the problem. Also, a new command line switch should be added
that allows the job to continue even if there is a problem contacting the Hudson
server.

ryan_shoemaker added a comment - 2007-02-26 11:03 The current code simply dumps a "java.net.ConnectException: Connection timed out " stacktrace if it is unable to contact the Hudson server and terminates without running the underlying job. This should be improved by printing a warning message explaining the problem. Also, a new command line switch should be added that allows the job to continue even if there is a problem contacting the Hudson server.

Alan Harder added a comment - 2009-12-03 09:53

Marking unassigned, as no updates in a long time.

Alan Harder added a comment - 2009-12-03 09:53 Marking unassigned, as no updates in a long time.

People

Assignee:: Unassigned

Reporter:: ryan_shoemaker

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2007-02-26 10:50

Updated:: 2013-08-22 15:59