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

Incorrect local modification being identified when svn:keywords are used on 1.8

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • subversion-plugin
    • None
    • jenkins 1.583
      subversion-plugin 2.5

      We have just upgraded jenkins from using 1.5 subversion clients to using 1.8

      When jenkins checks out a project that has files using svn:keywords it is incorrectly identifying local changes. The revision number in the file is being indicated as the n-1 time the file was physically changed and not the last time.

      When the project is checked out using command line svn 1.8.13 the files are checked out correctly with no local changes, so there appears to be a difference between jenkins svn and installed svn.

          [JENKINS-28749] Incorrect local modification being identified when svn:keywords are used on 1.8

          Appears to be fixed in svnkit: https://issues.tmatesoft.com/issue/SVNKIT-514

          unfortunately no mention of version numbers there, but in their changelog:

          == version 1.8.9 ==
          + Support for Subversion 1.8 ephemeral transaction properties.

          Rene Affourtit added a comment - Appears to be fixed in svnkit: https://issues.tmatesoft.com/issue/SVNKIT-514 unfortunately no mention of version numbers there, but in their changelog: == version 1.8.9 == + Support for Subversion 1.8 ephemeral transaction properties.

          dan_smartstream Could you provide a step by step process in order to reproduce the bug?

          Manuel Recena Soto added a comment - dan_smartstream Could you provide a step by step process in order to reproduce the bug?

          dan_smartstream I could not reproduce the bug. I followed this steps:

          1. Configure Jenkins to work with subversion workspace version 1.8
          2. Add a freestyle project
          3. Configure a subversion repository protected
          4. Configure a credentials for this repository
          5. Build the project

          Environment: Jenkins 1.613 + Subversion Plugin 2.5.1
          This repository had files using SVN Keyword Substitution (svn:keywords)

          Manuel Recena Soto added a comment - dan_smartstream I could not reproduce the bug. I followed this steps: Configure Jenkins to work with subversion workspace version 1.8 Add a freestyle project Configure a subversion repository protected Configure a credentials for this repository Build the project Environment: Jenkins 1.613 + Subversion Plugin 2.5.1 This repository had files using SVN Keyword Substitution (svn:keywords)

          dan_smartstream, Could you provide any feedback?

          Manuel Recena Soto added a comment - dan_smartstream , Could you provide any feedback?

            recena Manuel Recena Soto
            dan_smartstream dan russell
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: