[JIRA] (JENKINS-17267) Git clean or wipeout workspace follows junction on Windows slaves
Title: Message Title Mark Waite closed an issue as Won't Fix Jenkins / JENKINS-17267 Git clean or wipeout workspace follows junction on Windows slaves Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.148100.1363689564000.14754.1571794279839%40Atlassian.JIRA.
[JIRA] (JENKINS-17267) Git clean or wipeout workspace follows junction on Windows slaves
Title: Message Title Jesse Glick commented on JENKINS-17267 Re: Git clean or wipeout workspace follows junction on Windows slaves Avoid using junctions or symbolic links. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17267) Git clean or wipeout workspace follows junction on Windows slaves
Title: Message Title pjdarton edited a comment on JENKINS-17267 Re: Git clean or wipeout workspace follows junction on Windows slaves [~jglick] I think that this one has been resolved by JENKINS-29956.FYI advising folks "to not use junctions" isn't viable - you might as well advise folks not to use Windows :-)Windows has hard-coded functionality preventing most people from creating Symbolic Links (you need to be a *non-admin* user who's been granted the right to create symbolic links, or you need to be running "as administrator" with no protection) and so the only remaining option is to use a "directory junction" (which anyone can create) .It's a pain in the ^%$£ but it's the only option for most users on Windows. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17267) Git clean or wipeout workspace follows junction on Windows slaves
Title: Message Title pjdarton commented on JENKINS-17267 Re: Git clean or wipeout workspace follows junction on Windows slaves Jesse Glick I think that this one has been resolved by JENKINS-29956. FYI advising folks "to not use junctions" isn't viable - Windows has hard-coded functionality preventing most people from creating Symbolic Links (you need to be a non-admin user who's been granted the right to create symbolic links, or you need to be running "as administrator" with no protection) and so the only option is to use a "directory junction". It's a pain in the ^%$£ but it's the only option for most users on Windows. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
