Hi Bob, You could package it up in an extension (plugin). See https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin#BuildFlowPlugin-ExtensionPoint
/James From: [email protected] [mailto:[email protected]] On Behalf Of Bob Bick Sent: 28 August 2013 15:51 To: [email protected] Subject: RE: Build Flow Plugin - Groovy libraries After thinking about this a little more, I think that the best workaround is to treat Jobs as libraries. The Build Flow job can invoke "common library" jobs that can execute Groovy code. Bob From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Bob Bick Sent: Wednesday, August 28, 2013 10:24 AM To: [email protected]<mailto:[email protected]> Subject: Build Flow Plugin - Groovy libraries Hi, I have been using the Build Flow Plugin for a while now, and it works great. I have multiple Build Flow Plugin jobs that have common groovy code that I'd like to put into a Groovy library (call it Library.groovy). The Build Flow Plugin uses groovy.lang.GroovyShell to execute the groovy code and I have not found a way to have it include common groovy library code. Has anyone found a way to include common Groovy library code into multiple Build Flow Plugin jobs? I don't think it is possible, but then again, I may be missing something. Thanks for your time, Bob -- 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.
