Re: [workflow plugin] loop stops at first iteration as it seems...

BTW I'm using workflow plugin 1.3 version straight from github. On Thursday, February 5, 2015 at 11:20:53 PM UTC-8, Shane Kim wrote: > > Hi, > > I'm not sure if workflow plugin is limiting iteration or not, I found it > really odd... > > I have this simple

[workflow plugin] loop stops at first iteration as it seems...

Hi, I'm not sure if workflow plugin is limiting iteration or not, I found it really odd... I have this simple code... def cdir = new File('.') cdir.eachFileRecurse(FileType.FILES) { file -> // or eachFile method println file.getName() } When I execute the code on straight command line I

Re: [workflow plugin] list files in workspace

l return it for you. > > On 4 February 2015 22:28:49 GMT+00:00, Shane Kim > wrote: >> >> maybe it's simple thing but I just couldn't find or get it working. How >> would I get the current workspace directory path? >> I've tried these: >> >> env

[workflow plugin] list files in workspace

maybe it's simple thing but I just couldn't find or get it working. How would I get the current workspace directory path? I've tried these: env.WORKSPACE // gives me null new File('.') // gives me Jenkins installation path rather than workspace ws { new File('.') } // gives me Jenkins installatio

requirements for downstream builds

Hi Jenkins users, I'm really confused with Downstream builds information on a build page. I have an upstream job and a downstream job. Downstream job is a deployment job and upstream job is a job that pulls source code and then archive .zip file. The zip file gets copied from upstream job to do

Best practices in re-using binaries from upstream job

Hello Jenkis users, I'm wondering if there is a good best practices in file sharing between jobs. I have this setup right now. A. Upstream job A pulls files from Team Foundation Server's drop location (they are over 100MB+ easily, eventually we want to compile MS project in jenkins we can not r