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

maven build creates symlinkd files that Windows OS does not understand

    Details

    • Similar Issues:

      Description

      After upgrading to 1.509.4 our Maven builds create files that Windows cannot backup. The invalid files are SYMLINKD one for each module.
      The maven build and UI seem to work fine. The files are under the jobs/project name/builds/buildnumber or builddate directory.

      11/19/2013 04:47 PM <SYMLINKD> us.mn.state.education.sfin.automation$sfi
      n-post-processor [../../modules/us.mn.state.education.sfin.automation$sfin-post-
      processor/builds/2013-11-19_16-40-46]
      4 File(s) 3,881,255 bytes
      34 Dir(s) 20,236,365,824 bytes free

      E:\jenkins\.jenkins\jobs\SFIN-OB\builds\56>type us.mn.state.education.sfin$confi
      gs
      Access is denied.

      E:\jenkins\.jenkins\jobs\SFIN-OB\builds\56>cd us.mn.state.education.sfin$configs

      The filename, directory name, or volume label syntax is incorrect.

      E:\jenkins\.jenkins\jobs\SFIN-OB\builds\56>

        Attachments

          Issue Links

            Activity

            Hide
            jglick Jesse Glick added a comment -

            First of all, I doubt this has anything to do with the Maven plugin. Jenkins core creates build number symlinks.

            Second, what is the actual bug here? That some old Windows backup programs cannot handle symlinks even when the Windows kernel/filesystem can produce them? That is the fault of the backup program, not Jenkins.

            Show
            jglick Jesse Glick added a comment - First of all, I doubt this has anything to do with the Maven plugin. Jenkins core creates build number symlinks. Second, what is the actual bug here? That some old Windows backup programs cannot handle symlinks even when the Windows kernel/filesystem can produce them? That is the fault of the backup program, not Jenkins.
            Hide
            jknudsen Joe Knudsen added a comment - - edited

            Jesse it is not the build number links that are problematic. The Maven build includes a section called Module Builds. The plugin seems to create a link for each Module. These module links are the problem. The Windows OS does not see the links as valid. I believe the links contain a path and the path uses the wrong path separator for Windows. I do not see any impacts in the Jenkins UI. I Jenkins is not impacted because Jenkins uses Java and Java can handle either Windows or Unix file separators. The problem is the Windows OS and backup software see these as corrupted files. Hope this helps.

            Show
            jknudsen Joe Knudsen added a comment - - edited Jesse it is not the build number links that are problematic. The Maven build includes a section called Module Builds. The plugin seems to create a link for each Module. These module links are the problem. The Windows OS does not see the links as valid. I believe the links contain a path and the path uses the wrong path separator for Windows. I do not see any impacts in the Jenkins UI. I Jenkins is not impacted because Jenkins uses Java and Java can handle either Windows or Unix file separators. The problem is the Windows OS and backup software see these as corrupted files. Hope this helps.
            Hide
            tpilz Thomas Pilz added a comment -

            Hi there, i still hope that there will be some Progress on this Issue as this Problem is a real Blocker for Windows backed Jenkins Installations with Maven Projects.
            Backups via ZIP/TAR and also Job Migration via copy of Jobs Folder to different Host is not working at the moment due to wrong generated symbolic links.

            09.09.2014 14:17 <SYMLINKD> com.foo.acme$acmeCore [../../modules/com.foo.acme$acmeCore/builds/2014-09-09_14-16-18]

            should be

            09.09.2014 14:17 <SYMLINKD> com.foo.acme$acmeCore [..\..\modules\com.foo.acme$acmeCore\builds\2014-09-09_14-16-18]

            Environment: Windows 2008 R2 / Jenkins 1.532.2 LTS / Maven Project Plugin 2.0.3 / Maven 3.2.1

            Show
            tpilz Thomas Pilz added a comment - Hi there, i still hope that there will be some Progress on this Issue as this Problem is a real Blocker for Windows backed Jenkins Installations with Maven Projects. Backups via ZIP/TAR and also Job Migration via copy of Jobs Folder to different Host is not working at the moment due to wrong generated symbolic links. 09.09.2014 14:17 <SYMLINKD> com.foo.acme$acmeCore [../../modules/com.foo.acme$acmeCore/builds/2014-09-09_14-16-18] should be 09.09.2014 14:17 <SYMLINKD> com.foo.acme$acmeCore [..\..\modules\com.foo.acme$acmeCore\builds\2014-09-09_14-16-18] Environment: Windows 2008 R2 / Jenkins 1.532.2 LTS / Maven Project Plugin 2.0.3 / Maven 3.2.1
            Hide
            jknudsen Joe Knudsen added a comment -

            Thomas we ended up excluding the build folders from our backups. Would like to see this resolved and be able to do a complete Jenkins backup.

            Show
            jknudsen Joe Knudsen added a comment - Thomas we ended up excluding the build folders from our backups. Would like to see this resolved and be able to do a complete Jenkins backup.
            Hide
            tpilz Thomas Pilz added a comment -

            Our Jenkins Instance is growing and we would like to move from VM to Hardware. This Bug makes it impossible to transfer the Jobs to the new Instance without Data loss.

            Show
            tpilz Thomas Pilz added a comment - Our Jenkins Instance is growing and we would like to move from VM to Hardware. This Bug makes it impossible to transfer the Jobs to the new Instance without Data loss.

              People

              • Assignee:
                Unassigned
                Reporter:
                jknudsen Joe Knudsen
              • Votes:
                3 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: