Re: Pipeline - how to copy a directory of files from outside of workspace into a workspace using groovy?

2017-08-03 Thread Stephen Connolly
On Thu 3 Aug 2017 at 21:09, bbyjenkns wrote: > You can't use normal groovy api since it only works on master. Since >> you're already using unix slaves, just use a normal shell step will save >> you headaches. > > > Why does the groovy api only work on master, but the sh step

Re: Pipeline - how to copy a directory of files from outside of workspace into a workspace using groovy?

2017-08-03 Thread bbyjenkns
> > You can't use normal groovy api since it only works on master. Since > you're already using unix slaves, just use a normal shell step will save > you headaches. Why does the groovy api only work on master, but the sh step does? What is the point of having a global pipeline if it can

Re: Pipeline - how to copy a directory of files from outside of workspace into a workspace using groovy?

2017-08-02 Thread jerome
It's not as funny as it should be for a build system manipulating file should be fairly easy. There is no direct way, but here a solution that would probably work I haven't test it: 1. Zip the folder into a single file from the particular source node 2. statch the file (or maybe if the

Re: Pipeline - how to copy a directory of files from outside of workspace into a workspace using groovy?

2017-08-02 Thread Cuong Tran
You can't use normal groovy api since it only works on master. Since you're already using unix slaves, just use a normal shell step will save you headaches. On Wednesday, August 2, 2017 at 7:26:01 AM UTC-7, bbyjenkns wrote: > > We have a somewhat different use case where we have a bunch of

Pipeline - how to copy a directory of files from outside of workspace into a workspace using groovy?

2017-08-02 Thread bbyjenkns
We have a somewhat different use case where we have a bunch of common config and build related files on NFS mount that need to be copied into each build workspace. What I need to do is copy a directory out of this NFS location and into workspaces as needed, a different directory per build