Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-330

External jobs should not fail if server is down

    XMLWordPrintable

Details

    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

          Activity

            mindless Alan Harder added a comment -

            Marking unassigned, as no updates in a long time.

            mindless Alan Harder added a comment - Marking unassigned, as no updates in a long time.

            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 ryan_shoemaker added a comment - 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.

            People

              Unassigned Unassigned
              ryan_shoemaker ryan_shoemaker
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: