this is a voluntary limitation. Even flow uses groovy, it's supposed to be a DSL, not a system groovy script. Use scriptler/groovy plugin/etc if you want to do such thing
2013/9/18 Schalk Cronjé <[email protected]> > With Build Flow Plugin you can only access Groovy modues that Jenkins > System Groovy has access to. You cannot use @Grab to pull in extra modules. > This is a limitation of Build Flow Plugin IMHO, but Nicolas does not agree > - https://groups.google.com/forum/#!topic/jenkinsci-users/2XFDB5g7O7A). > > That is the reason that I do the copying in a seperate job - IN the end > that paid off better for my specific cases. > > Hwowever it is possible to get hold of different plugin within Build Flow, > I am not sure how much success you'll be able to achieve via this route > though. BY using getAction i.e. > > def foobar=build.getAction(hudson.scm.RevisionParameterAction.class) // > Replace with appropriate class name > > > you might be able to play around enough to get something to work. > > > > On Tuesday, 17 September 2013 19:51:59 UTC+1, LesMikesell wrote: >> >> On Tue, Sep 17, 2013 at 10:06 AM, Schalk Cronjé <[email protected]> >> wrote: >> > This blog post might be insightful - >> > http://delivervalue.blogspot.**co.uk/2013/06/more-advanced-** >> build-flows-with-jenkins.html<http://delivervalue.blogspot.co.uk/2013/06/more-advanced-build-flows-with-jenkins.html> >> > >> > It does show you how to run a number of similar jobs in parallel and >> then >> > send the resulting build numbers to a downstream job. >> > >> > It does not, however, show you how to download artifacts from these >> builds. >> > This cannot be achieved by Copy Artifact Plugin as one has to loop >> around >> > the build numbers (assuming they are from the same job). A simple >> Gradle >> > build step or a Groovy build step can achieve this for you. >> >> But I don't see 'add build step' in a build flow job - just the flow >> dsl and post-build actions. I do have 'copy files back to the job's >> workspace on the master node' in the post-build choices that might be >> coming from the 'copy to slave' plugin, but none of my jobs run on the >> master node so that doesn't make sense. (But maybe I could run the >> build flow jobs there if that would make it work...). >> >> Is it possible to do the copy within the build flow dsl itself? It >> seems to handle some groovy stuff. >> >> -- >> Les Mikesell >> [email protected] >> > -- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
