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

Jenkins 1.478 fails on SVN update

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None
    • Microsoft Windows Server 2003

      Seems like when using SVN checkout strategy "Emulate clean checkout by first deleting unversioned/ignored files then svn update" deleting of files on a long path fails. E.g.:

      org.tmatesoft.svn.core.SVNException: svn: Unable to delete D:\ws\product_xxxxx_yyy_ALL\building\Maven\com.xxxxxx.xxxproduct\target\products\com.xxxxxx.xxx_xxx_xxx.product\win32\win32\x86\features\com.xxxxxx.xxx.xxxx.advanced.feature_1.1.4.201208300230\META-INF\maven\com.xxxxxx.xxxx_plugins\com.xxxxxx.xxx.xxxx.advanced.feature - files in dir: [D:\ws\product_xxxxx_yyy_ALL\building\Maven\com.xxxxxx.xxxproduct\target\products\com.xxxxxx.xxx_xxx_xxx.product\win32\win32\x86\features\com.xxxxxx.xxx.xxxx.advanced.feature_1.1.4.201208300230\META-INF\maven\com.xxxxxx.xxxx_plugins\com.xxxxxx.xxx.xxxx.advanced.feature\pom.properties, D:\ws\product_xxxxx_yyy_ALL\building\Maven\com.xxxxxx.xxxproduct\target\products\com.xxxxxx.xxx_xxx_xxx.product\win32\win32\x86\features\com.xxxxxx.xxx.xxxx.advanced.feature_1.1.4.201208300230\META-INF\maven\com.xxxxxx.xxxx_plugins\com.xxxxxx.xxx.xxxx.advanced.feature\pom.xml]

      Deleting of the same file is successful when using Jenkins 1.474 version.

            Unassigned Unassigned
            katalin_boros Katalin Boros
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: