|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
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.
Replicated problem with workspace cleanup 0.20, Jenkins 1.554.1-LTS and SSH slaves 1.6.
In the default mode without any include/exclude ant patterns the symlinks are NOT followed.
Using the "advanced" include/exclude ant patterns causes the plugin to follow symlinks outside of the workspace and can potentially delete a lot of data.
Also if only adding a single exclude "foobar" rule, the default non specified include will follow symlinks.
All the tools and libraries I have used so far for deleting entire directory structures (python shutil.rmtree, rm -r, etc...) are not following symlinks per default.
Thankfully we had recent automatic snapshot backups of the non workspace data.
An accidental symlink to the "/" directory is significant for installations with large NFS mounts. Even with backups or snapshots, it causes downtime for restoration.
I would call this dangerous behavior and not just weird behavior.