• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • jira-plugin
    • None
    • Windows Server 2008 R2
      Jenkins ver. 1.651
      Jira-Plugin ver. 2.2.1

      I cannot connect to our Atlassian OnDeman Jira instance. From Jenkins > Manage Jenkins > Configure System, the following settings are configured:
      URL: https://company.atlassian.net/
      Link URL: <blank>
      Use HTTP auth: false
      Supports Wiki Notation: false
      Record SCM Changes: true
      Issue Pattern: <blank>
      username: user
      password: password
      Connection timeout: 10
      Visible for Group: <blank>
      Visible for Project Role: <blank>
      Add Timestamp to JIRA comments: false
      Jira comments timestamp format: <blank>

      When I hit "Validate Settings" I receive an ERROR link that gives me a java.net.SocketTimeoutException, stack trace is in the file attached.

      Things I have tried:
      1. Making sure Jenkins user can access URL from that server, works fine in web browser.
      2. Changing proxy settings to configure as a no proxy host, both in jenkins and on server.
      3. Increasing the value of connection Timeout, has no affect.
      4. Falling back to the previously working Jira plugin. This just led to a new error.
      5. Making sure rest is enabled, hitting /rest/api/latest/issue/TES-1 returns successful.

      The last time that this was working for me was September 1, 2015, with jira plugin ver. 1.39 and whatever the latest OnDemand Jira instance was at the time. No configuration should have changed on Jenkins or Jira since then, just versions. Any suggestions for further troubleshooting would be greatly appreciated.

          [JENKINS-34457] Jira REST SocketTimeoutException

          1. have you checked if you can access JIRA URL e.g. via CURL from the jenkins server?
          2. Are you using proxy?

          Radek Antoniuk added a comment - 1. have you checked if you can access JIRA URL e.g. via CURL from the jenkins server? 2. Are you using proxy?

          Shawn Cole added a comment -

          1. I have remote into the server with the account Jenkins runs under, and I am able to access REST urls through the browser. I am not sure how I can simulate a curl on windows machine.
          2. That browser does have proxy settings, and company policy dictates we need to use the proxy, or requests won't go out, which may be what is happening here. Is there a way I can configure this plugin to use proxy information with credentials?

          Shawn Cole added a comment - 1. I have remote into the server with the account Jenkins runs under, and I am able to access REST urls through the browser. I am not sure how I can simulate a curl on windows machine. 2. That browser does have proxy settings, and company policy dictates we need to use the proxy, or requests won't go out, which may be what is happening here. Is there a way I can configure this plugin to use proxy information with credentials?

          So this might be JENKINS-25829...

          Radek Antoniuk added a comment - So this might be JENKINS-25829 ...

          Amit Kushwaha added a comment -

          I was also facing the same issue, I updated the 'connection timeout' and 'read timeout' to 1000 and it worked for me.

          Amit Kushwaha added a comment - I was also facing the same issue, I updated the 'connection timeout' and 'read timeout' to 1000 and it worked for me.

            Unassigned Unassigned
            cole9350 Shawn Cole
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: