Just realized the same thing, after developing my JenkinsFile inline with sandbox removed, then approved the whole operation into white listing. That @script folder was unexpected for the least I could say
On Monday, August 1, 2016 at 7:30:04 PM UTC-4, Peter Wiseman wrote: > > Likewise, I'm concerned about a full checkout into workspace@script. > Seems to be overkill if it's just to find the Jenkinsfile. With multiple > active branches (each 3GB), that's seemingly quite a lot of unnecessary > permanent storage. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/49c40d0a-07fb-412d-b678-ec852e6b2a17%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
