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

When repository URL contains variable causes checkout from wrong SVN path

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None
    • Ubuntu server 12.04
      Jenkins 1.518
      Subversin Plugin 1.50

      When svn location path contains variable, then jenkins checkout the code from trunk.

      This is the ulr configured in Jenkins for SVN location:
      https://svn.mydomain.com/project/branches/build-${SOURCE_BUILD_NUMBER}

      But instead checkout from specified branch "build-1.1.50.1-B100" runtime, it's checked from from /trunk.
      The build log shows that checkout is from the expected branch, but checking the svn info on workspace claims the code comes from /trunk

      • Piece of console log
        Building on master in workspace /var/lib/jenkins/jobs/project-quality/workspace
        Cleaning local Directory .
        Checking out https://svn.mydomain.com/project/branches/build-1.1.50.1-B100 at revision '2013-06-20T10:10:44.030 +0300'
        
      • svn info
        root@jenkins2:/var/lib/jenkins/jobs/project-quality/workspace# svn info
        Path: .
        Working Copy Root Path: /var/lib/jenkins/jobs/project-quality/workspace
        URL: https://svn.mydomain.com/project/trunk
        Repository Root: https://svn.mydomain.com/project
        Repository UUID: adda5579-93c7-304f-a113-a437aa8ac68b
        Revision: 11227
        Node Kind: directory
        Schedule: normal
        Last Changed Author: username
        Last Changed Rev: 11224
        Last Changed Date: 2013-06-20 09:33:38 +0300 (Thu, 20 Jun 2013)
        

          [JENKINS-18426] When repository URL contains variable causes checkout from wrong SVN path

          Ron Bierman added a comment -

          I tried to reproduce your issue but I'm not able to.

          • Do you have jenkins slaves running?
          • What SVN workspace version are you using?

          Ron Bierman added a comment - I tried to reproduce your issue but I'm not able to. Do you have jenkins slaves running? What SVN workspace version are you using?

          hi Ron,

          yes there are 2 slaves configured, running long time consuming automated tests. But non of them have installed svn (only jenkins)
          Issue appeared after latest update on jenkins and subversion pluging.

          Svn version:

          svn, version 1.7.9 (r1462340)
             compiled Apr 19 2013, 20:21:20
          

          Thanks

          Georgi Georgiev added a comment - hi Ron, yes there are 2 slaves configured, running long time consuming automated tests. But non of them have installed svn (only jenkins) Issue appeared after latest update on jenkins and subversion pluging. Svn version: svn, version 1.7.9 (r1462340) compiled Apr 19 2013, 20:21:20 Thanks

          René Zanner added a comment -

          I have the same issue here. Jenkins reports checking out the desired tag (which contains a variable, that by itself contains the build number of the triggering build), but uses trunk instead (checked with svn info in file system).

          Is there some default, that falls back to trunk? I would rather let this build fail, when the checkout of the tag fails.

          René Zanner added a comment - I have the same issue here. Jenkins reports checking out the desired tag (which contains a variable, that by itself contains the build number of the triggering build), but uses trunk instead (checked with svn info in file system). Is there some default, that falls back to trunk? I would rather let this build fail, when the checkout of the tag fails.

          Cosmin Diga added a comment -

          The same issue here:
          Jenkins reports checking out the desired tag (which contains a variable, that by itself contains the build number of the triggering build), but uses trunk instead (checked with svn info in file system).

          svn plugin version 2.4.5; single node

          Cosmin Diga added a comment - The same issue here: Jenkins reports checking out the desired tag (which contains a variable, that by itself contains the build number of the triggering build), but uses trunk instead (checked with svn info in file system). svn plugin version 2.4.5; single node

          Vikram Garg added a comment -

          We are also facing exact issue. where when branch name is passed as variable then Jenkins reports that desired branch is getting checked out. but review the workspace confirms that its form trunk. Is someone looking into the issue.

          Vikram Garg added a comment - We are also facing exact issue. where when branch name is passed as variable then Jenkins reports that desired branch is getting checked out. but review the workspace confirms that its form trunk. Is someone looking into the issue.

            Unassigned Unassigned
            georgi_georgiev Georgi Georgiev
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: