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

Wrong "svn info" command causes error when checking out subversion project

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Platform: PC, OS: Windows XP

      When I try the 1st build of my project, the "svn co" command works, but after
      that a "svn info trunk" is issued, which should be only "svn info" (no "trunk"),
      because there´s no "trunk" directory since I am already downloading the code
      from trunk. I suspect this is caused by a erroneous CVS behavior inheritage.

      Here´s the console output:

      [workspace] $ svn co -q --non-interactive https://trac/svn/infopae/trunk
      $ svn info trunk
      ERROR: no revision in the svn info output
      java.io.IOException: no revision in the svn info output
      at hudson.scm.SubversionSCM$SvnInfo.parse(SubversionSCM.java:222)
      at hudson.scm.SubversionSCM.buildRevisionMap(SubversionSCM.java:246)
      at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:162)
      at hudson.model.Project.checkout(Project.java:252)
      at hudson.model.Build$1.run(Build.java:134)
      at hudson.model.Run.run(Run.java:460)
      at hudson.model.Build.run(Build.java:116)
      at hudson.model.Executor.run(Executor.java:54)

          [JENKINS-77] Wrong "svn info" command causes error when checking out subversion project

          I debugged the application and was abble to diagnose the problem more precisely now.

          The problem relies in the fact that my LANG is set to pt_BR making "svn info
          trunk" produce a localized output which Hudson is unable to parse.

          Maybe a more reliable way to obtain the revision information would be to use
          "svn log" command with the --xml option the same way CruiseControl does.

          demetriusnunes added a comment - I debugged the application and was abble to diagnose the problem more precisely now. The problem relies in the fact that my LANG is set to pt_BR making "svn info trunk" produce a localized output which Hudson is unable to parse. Maybe a more reliable way to obtain the revision information would be to use "svn log" command with the --xml option the same way CruiseControl does.

          Indeed! Of course! I need to stop and think before implementing, you know.

          Kohsuke Kawaguchi added a comment - Indeed! Of course! I need to stop and think before implementing, you know.

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

              Created:
              Updated:
              Resolved: