Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: maven-invoker-plugin, maven-plugin
-
Labels:
-
Environment:Windows 2008 R2 Jenkins 1.509.4
-
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
- is related to
-
JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows
-
- Resolved
-
-
JENKINS-22803 'JellyTagException: <st:include> For input string: ""' on job view
-
- Resolved
-
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.