Steps to reproduce:

1. Open slave command prompt
   > mkdir C:\test
   > cd /d C:\test
   > notepad file.txt
2. Write something, save
   > mklink linked.txt file.txt
3. Note linked.txt is an NTFS symlink

1. Open Jenkins web interface
2. New Job
3. Name 'test'
4. 'Build a free-style software project'
5. OK button
6. Check 'Restrict where this project can be run', enter Windows slave name
7. Check 'Use custom workspace', enter Directory: C:\test
8. Check 'Archive the artifacts', enter Files to archive: file.txt,linked.txt
9. Save button
10. Build Now link
11. When complete, click the link for Build #1
12. Note 'linked.txt' appears with a size 0, while file.txt is size 15 bytes
13. 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 ?