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

System setting http.nonProxyHosts not handled properly

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Blocker Blocker
    • subversion-plugin
    • subversion plugin 1.39, 1.45
      jenkins 1.508
      uberSVN WANdisco 2013 - #13.2-3153 SVN - 1.7
      openSuSe

      The system parameter http.nonProxyHosts managed by uberSVN is not resolved correctly by the Jenkins subversion plugin.

      For instance the setting: .intranet|localhost|127.0.0.1 only works for localhost and 127.0.0.1, no proxy bypass is done for servers in the intranet belonging to the domain .intranet.

          [JENKINS-17448] System setting http.nonProxyHosts not handled properly

          Pim Do added a comment -

          Ok, I'm still waiting on a solution on non proxy hosts.
          Currently all checkouts fail because Jenkins or the Subversion plugin do not use the nonProxyHosts configured in tomcat (JAVA_OPTS) nor the system (openSuSe: NO_PROXY).

          Pretty pretty please!!!!!

          Pim Do added a comment - Ok, I'm still waiting on a solution on non proxy hosts. Currently all checkouts fail because Jenkins or the Subversion plugin do not use the nonProxyHosts configured in tomcat (JAVA_OPTS) nor the system (openSuSe: NO_PROXY). Pretty pretty please!!!!!

          Marcelo Rebasti added a comment - - edited

          @Pim Do, the subversion plugin relies in svnkit for manage all the svn commands. According to the library documentation, svnkit uses the standard proxy configuration for svn clients.

          For the use case that you describe, you have to configure the http-proxy-exceptions property inside the "servers" file.

          In these pages there are more info about the topic and the location of servers file.

          http://svnkit.com/kb/user-guide-config-settings.html
          http://svnbook.red-bean.com/en/1.1/ch07.html#svn-ch-7-sect-1.3.1

          Best regards.

          Marcelo Rebasti

          Marcelo Rebasti added a comment - - edited @Pim Do, the subversion plugin relies in svnkit for manage all the svn commands. According to the library documentation, svnkit uses the standard proxy configuration for svn clients. For the use case that you describe, you have to configure the http-proxy-exceptions property inside the "servers" file. In these pages there are more info about the topic and the location of servers file. http://svnkit.com/kb/user-guide-config-settings.html http://svnbook.red-bean.com/en/1.1/ch07.html#svn-ch-7-sect-1.3.1 Best regards. Marcelo Rebasti

            mrebasti Marcelo Rebasti
            pim Pim Do
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: