Details

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.

Activity

@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:

Josh Santangelo
added a comment - 2014-01-10 22:22 @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.

looks right to me. There are no failed builds, which the bogus target -1 indicates. The last stable build is #162, so lastStableBuild links to that (which is itself a symlink to the actual build directory, 2014-01-10_12-58-51).

Whether or not the Explorer GUI allows (valid) symlinks to be traversed is a secondary consideration, so long as Jenkins code can read the symlink target.

Jesse Glick
added a comment - 2014-01-10 22:57 <SYMLINK> lastFailedBuild [-1] <SYMLINKD> lastStableBuild [162]
looks right to me. There are no failed builds, which the bogus target -1 indicates. The last stable build is #162, so lastStableBuild links to that (which is itself a symlink to the actual build directory, 2014-01-10_12-58-51 ).
Whether or not the Explorer GUI allows (valid) symlinks to be traversed is a secondary consideration, so long as Jenkins code can read the symlink target.

Josh Santangelo
added a comment - 2014-01-10 23:09 You know, you're right. I was misinterpreting that number. This should work fine for my needs.
The issue with explorer not following the links by default is real, though.

If you can find a command which can be run as the Jenkins user which detects whether the fsutil command needs be run (as an administrator), file an RFE for Jenkins to warn you of this, most simply via a console warning but ideally using an AdministrativeMonitor. (Even better would be for Jenkins to offer to run it after you supply an administrator login, using the Windows equivalent of sudo if there is such a thing.)

Jesse Glick
added a comment - 2014-01-13 15:17 If you can find a command which can be run as the Jenkins user which detects whether the fsutil command needs be run (as an administrator), file an RFE for Jenkins to warn you of this, most simply via a console warning but ideally using an AdministrativeMonitor . (Even better would be for Jenkins to offer to run it after you supply an administrator login, using the Windows equivalent of sudo if there is such a thing.)