-
Bug
-
Resolution: Unresolved
-
Major
-
Windows 2008 R2 Jenkins 1.509.4
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>
- 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
-
[JENKINS-20725] maven build creates symlinkd files that Windows OS does not understand
Summary | Original: maven build creates files that Windows cannot backup | New: maven build creates symlinkd files that Windows OS does not understand |
Component/s | New: maven [ 16033 ] | |
Component/s | Original: maven2 [ 15487 ] |
Labels | New: maven |
Component/s | New: maven2 [ 15487 ] |
Affects Version/s | New: current [ 10162 ] |
Link |
New:
This issue is related to |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
After looking closer I see that the slashes are Unix forward slashes in for the path to the symbolic link. Two directories above is a SYMLINK for lastStable and that uses the back slashes. I am guessing the Maven plugin needs to start using the forward slashes on Windows. I did check and the files exist if I use the back slashes.