RE: Build Flow Plugin - Groovy libraries

To: jenkinsci-users@googlegroups.com 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:

RE: Build Flow Plugin - Groovy libraries

Thanks James. From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of James Nord (jnord) Sent: Wednesday, August 28, 2013 11:09 AM To: jenkinsci-users@googlegroups.com Subject: RE: Build Flow Plugin - Groovy libraries Hi Bob, You could package it up in an

RE: Build Flow Plugin - Groovy libraries

f Bob Bick Sent: Wednesday, August 28, 2013 10:24 AM To: jenkinsci-users@googlegroups.com 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'

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 cod