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

proxied access to http subversion repository fails

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Platform: All, OS: All

      I installed a vanilla windows 2003 x64.
      all there is on the box is java 5,6, 7, ant 1.7 and tomcat 6.0.7.
      I figured now that hudson integrates svnkit I don't need to install subversion
      on this box anymore.

      When I create a new project and try to authenticate I get the following message.
      Error
      svn: Unable to create SVNRepository object for
      'https://opends.dev.java.net/svn/opends/trunk/opends'

      nothing is logged ...

      could that be a security restriction on my end ?

      secondly, I installed subversion on this windows box but that does not help

          [JENKINS-245] proxied access to http subversion repository fails

          al_xipe added a comment -

          ok, looking more into this I figured what the problem was: proxy settings.
          since there is no subversion on my machine there is no default "servers" file
          created.
          not sure how we can go around this.
          Is there a way to set the proxy for svnkit without having to manually alter (or
          create for that matter) a file on the disk (or create a file where hudson can
          reach it) ?

          al_xipe added a comment - ok, looking more into this I figured what the problem was: proxy settings. since there is no subversion on my machine there is no default "servers" file created. not sure how we can go around this. Is there a way to set the proxy for svnkit without having to manually alter (or create for that matter) a file on the disk (or create a file where hudson can reach it) ?

          svnkit website has this document:
          http://svnkit.com/kb/user-guide-config-settings.html

          can you check if this fixes your problem? if it works, then we just need to
          create a web ui frontend for this file.

          Kohsuke Kawaguchi added a comment - svnkit website has this document: http://svnkit.com/kb/user-guide-config-settings.html can you check if this fixes your problem? if it works, then we just need to create a web ui frontend for this file.

          I put myself in the proxied environment but I couldn't reproduce the problem. I
          got an error indicating that PROPFIND failed, which is really more or less the
          same error message the command line svn gives you.

          Furthermore, when subversion configuration directory is not present, svnkit
          creates one for you (see SVNConfigFile.createDefaultConfiguration) So even if
          your system doesn't have subversion installed, that shouldn't have been a problem.

          I updated Hudson so that it does a better job at diagnosing the subversion
          error. It logs the failures now, and you can see the entire message in the
          config page.

          So please try the latest snapshot and let me know the exact error message and
          stack trace you get.

          Kohsuke Kawaguchi added a comment - I put myself in the proxied environment but I couldn't reproduce the problem. I got an error indicating that PROPFIND failed, which is really more or less the same error message the command line svn gives you. Furthermore, when subversion configuration directory is not present, svnkit creates one for you (see SVNConfigFile.createDefaultConfiguration) So even if your system doesn't have subversion installed, that shouldn't have been a problem. I updated Hudson so that it does a better job at diagnosing the subversion error. It logs the failures now, and you can see the entire message in the config page. So please try the latest snapshot and let me know the exact error message and stack trace you get.

          Fixed in 1.76.
          The problem was that Hudson wasn't initializing subversion transports until at
          least one build is tried with subversion. This causes failures if configuration
          of projects are attempted before any build runs.

          Kohsuke Kawaguchi added a comment - Fixed in 1.76. The problem was that Hudson wasn't initializing subversion transports until at least one build is tried with subversion. This causes failures if configuration of projects are attempted before any build runs.

            Unassigned Unassigned
            al_xipe al_xipe
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: