-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Windows Slave:
- Windows Server 2008 R2 SP1 64 bit
- C: is NTFS filesystem
- Sun Java 1.6.0_20
Master:
- Jenkins 1.460
- Red Hat Enterprise Linux 5.5 64 bit
- Sun Java 1.6.0_20
Steps to reproduce:
- Open slave command prompt
> mkdir C:\test
> cd /d C:\test
> notepad file.txt - Write something, save
> mklink linked.txt file.txt - Note linked.txt is an NTFS symlink
- Open Jenkins web interface
- New Job
- Name 'test'
- 'Build a free-style software project'
- OK button
- Check 'Restrict where this project can be run', enter Windows slave name
- Check 'Use custom workspace', enter Directory: C:\test
- Check 'Archive the artifacts', enter Files to archive: file.txt,linked.txt
- Save button
- Build Now link
- When complete, click the link for Build #1
- Note 'linked.txt' appears with a size 0, while file.txt is size 15 bytes
- Click 'Console Output' link, errors seen: (artifact_exception.log is attached)
Expected behaviour is: make a copy of the symlinked file as a regular file
Below are some types of "link" you may wish to consider for MS Windows. Jenkins does not necessarily need to support all.
Should be transparent to applications:
- NTFS file and directory symlinks (Win Vista and later)
- junction points (also supported on Win XP, ...)
Non-transparent:
- Windows Explorer shortcuts (.lnk) ?
- Cygwin symlinks ?