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

error check on SVN module names are insufficient

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Blocker Blocker
    • core
    • None
    • Platform: Sun, OS: SunOS

      Maybe I should reword this first statement.
      the ckecout actually goes well and all my project bits get dumped on my drive
      locally.

      after the actual ckecout, an extra step checks for the svn file
      $ svn co -q --non-interactive http://samsonite.central.sun.com/svn DirectoryServer
      $ svn info svn
      ERROR: revision check failed

      this fails because on unix it's there as a hidden file named .svn (dot svn)

      /path/to/hudson/jobs/DS/workspace/DirectoryServer$ls -al | grep svn
      drwxr-xr-x 7 al145121 staff 512 May 19 19:10 .svn
      /path/to/hudson/jobs/DS/workspace/DirectoryServer$svn info .svn
      Path: .
      URL: http://my.subversion.server/svn
      Repository UUID: 80270577-44fa-0310-af59-d331026e8b94
      Revision: 805
      Node Kind: directory
      Schedule: normal
      Last Changed Author: myself
      Last Changed Rev: 805
      Last Changed Date: 2006-05-19 11:37:33 +0200 (Fri, 19 May 2006)
      Properties Last Updated: 2006-05-19 19:10:06 +0200 (Fri, 19 May 2006)

          [JENKINS-45] error check on SVN module names are insufficient

          Changing the subject from "subversion checkout fails on solaris" to "error check
          on SVN module names are insufficient".

          What do you specify as the SVN module names? Given your output, it looks like
          you had "http://samsonite.central.sun.com/svn DirectoryServer" whereas you
          probably needed "http://samsonite.central.sun.com/svn/DirectoryServer"

          If this was an issue, I think it's just a matter of improving the error
          detection code.

          Kohsuke Kawaguchi added a comment - Changing the subject from "subversion checkout fails on solaris" to "error check on SVN module names are insufficient". What do you specify as the SVN module names? Given your output, it looks like you had "http://samsonite.central.sun.com/svn DirectoryServer" whereas you probably needed "http://samsonite.central.sun.com/svn/DirectoryServer" If this was an issue, I think it's just a matter of improving the error detection code.

          al_xipe added a comment -

          as you suggested, I tried with http://samsonite.central.sun.com/svn/DirectoryServer
          but the correct url is really http://samsonite.central.sun.com/svn
          DirectoryServer separated by a whitespace (which by the way sucessfully checks
          the bits out -what fails is the 'svn info' command that hudson issues afterwards)
          DirectoryServer really is the module and not the repository.

          $ svn co -q --non-interactive http://samsonite.central.sun.com/svn/DirectoryServer
          svn: URL 'http://samsonite.central.sun.com/svn/DirectoryServer' doesn't exist
          ERROR: Subversion failed

          al_xipe added a comment - as you suggested, I tried with http://samsonite.central.sun.com/svn/DirectoryServer but the correct url is really http://samsonite.central.sun.com/svn DirectoryServer separated by a whitespace (which by the way sucessfully checks the bits out -what fails is the 'svn info' command that hudson issues afterwards) DirectoryServer really is the module and not the repository. $ svn co -q --non-interactive http://samsonite.central.sun.com/svn/DirectoryServer svn: URL 'http://samsonite.central.sun.com/svn/DirectoryServer' doesn't exist ERROR: Subversion failed

          > as you suggested, I tried with
          http://samsonite.central.sun.com/svn/DirectoryServer
          > but the correct url is really http://samsonite.central.sun.com/svn
          > DirectoryServer separated by a whitespace (which by the way sucessfully checks
          > the bits out -what fails is the 'svn info' command that hudson issues afterwards)
          > DirectoryServer really is the module and not the repository.

          I'm still not exactly sure how your modules are layed out, but
          if directory named 'DirectoryServer' doesn't exist in the
          http://samsonite.central.sun.com/svn,
          sounds like you should just have "http://samsonite.central.sun.com/svn" as the
          module names.

          If you look at the help string of "SVN modules", it says:

          URL of SVN module. Multiple URLs can be specified.

          The intended use of this field is that you specify URLs and URLs only.
          If you specify "http://samsonite.central.sun.com/svn DirectoryServer",
          The former token is URL but the latter is not. You'll specify two URLs
          only if you have two modules to check out, and it seems to me that
          that's not what you want here.

          The svn checkout command works only because I'm not checking errors
          correctly, and apparently there's a bug in handling multiple module
          URLs correctly in checking out modules.

          Kohsuke Kawaguchi added a comment - > as you suggested, I tried with http://samsonite.central.sun.com/svn/DirectoryServer > but the correct url is really http://samsonite.central.sun.com/svn > DirectoryServer separated by a whitespace (which by the way sucessfully checks > the bits out -what fails is the 'svn info' command that hudson issues afterwards) > DirectoryServer really is the module and not the repository. I'm still not exactly sure how your modules are layed out, but if directory named 'DirectoryServer' doesn't exist in the http://samsonite.central.sun.com/svn , sounds like you should just have "http://samsonite.central.sun.com/svn" as the module names. If you look at the help string of "SVN modules", it says: URL of SVN module. Multiple URLs can be specified. The intended use of this field is that you specify URLs and URLs only. If you specify "http://samsonite.central.sun.com/svn DirectoryServer", The former token is URL but the latter is not. You'll specify two URLs only if you have two modules to check out, and it seems to me that that's not what you want here. The svn checkout command works only because I'm not checking errors correctly, and apparently there's a bug in handling multiple module URLs correctly in checking out modules.

          al_xipe added a comment -

          ok, I think I should apologize for wasting your time on this.
          Actually, it works if I specify only the svn repository URL
          (http:/samsonite.central.sun.com/svn).
          the additional parameter is here to tell the subversion client to rename the
          output directory to DirectoryServer.
          so that when you issue the following command on the command line:
          svn co http://samsonite.central.sun.com/svn DirectoryServer
          it checks out the "svn" module and writes the checked out files to
          DirectoryServer directory instead of svn.

          marking this one as an invalid bug, sorry kohsuke

          al_xipe added a comment - ok, I think I should apologize for wasting your time on this. Actually, it works if I specify only the svn repository URL (http:/samsonite.central.sun.com/svn). the additional parameter is here to tell the subversion client to rename the output directory to DirectoryServer. so that when you issue the following command on the command line: svn co http://samsonite.central.sun.com/svn DirectoryServer it checks out the "svn" module and writes the checked out files to DirectoryServer directory instead of svn. marking this one as an invalid bug, sorry kohsuke

            kohsuke Kohsuke Kawaguchi
            al_xipe al_xipe
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: