Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
Windows Server 2008, NTFS, Jenkins runs as Windows Service
Description
The lastStable and LastSuccessful links are created as invalid symlinks with no destination under Windows. These Files cause the backup to fail, since they are not valid and cause all sorts of zip archivers to fail.
Attachments
Issue Links
- is duplicated by
-
JENKINS-17594 incessant jenkins.model.PeepholePermalink updateCache WARNINGS
-
- Resolved
-
- is related to
-
JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand
-
- Open
-
-
JENKINS-19741 Massive jobs execution causes issues in lastSuccessfulBuild permalink update
-
- Reopened
-
-
JENKINS-18866 Symlink prevens backup from ThinBackup
-
- Closed
-
- relates to
-
JENKINS-37862 Extract build symlink handling to a plugin
-
- Resolved
-
@jesse @joe – My apologies, I'm pretty new to Jenkins and I don't really know how Maven fits in. I'm not specifically doing anything with Maven, but maybe it's involved in all builds?
The behavior that I'm seeing is that these symlinks can't be followed in the Windows Explorer GUI without applying that fsutil command above. Further, if I look at them from a command line, I see this:
01/09/2014 05:22 PM <SYMLINK> lastFailedBuild [-1]
01/10/2014 01:02 PM <SYMLINKD> lastStableBuild [162]
01/10/2014 01:02 PM <SYMLINKD> lastSuccessfulBuild [162]
01/05/2014 03:14 PM <SYMLINK> lastUnstableBuild [-1]
01/09/2014 05:22 PM <SYMLINK> lastUnsuccessfulBuild [-1]
A regular symlink would show the target of the link instead of a numeric code. I am trying to parse the target in a deployment script.
If I should enter this bug elsewhere, let me know. Thanks for responding.