For the dev part, use an IDE with Groovy support, and load in the classpath the Jenkins core lib and possible plugins you wanna twiddle on. Maybe look also at the scriptler plugin.
In general, when you don't receive answers, it may help to rephrase or rethink the subject. >From outside, what you wanna do could look like what actually plugins are designed for: offering in an accessible way standard feature for all jobs and so on. So what you want is actually possibly developing a dedicated plugin for your additional features. Rewriting (or not, btw) your groovy script in Java would be very straightforward since this is actually the same thing you're calling. My 2 cents 2016-04-01 14:46 GMT+00:00 Mark Waite <[email protected]>: > I (and other readers of the list) have seen your question. I don't have > any insights to offer. > > On Fri, Apr 1, 2016 at 8:36 AM Guy Matz <[email protected]> wrote: > >> Is anyone getting this? :-( >> >> On Thu, Mar 31, 2016 at 4:06 PM, Guy Matz <[email protected]> wrote: >> >>> Anyone? Thanks again. >>> >>> On Wed, Mar 30, 2016 at 4:52 PM, Guy Matz <[email protected]> wrote: >>> >>>> Hi! I have some groovy methods that I would like to make generally >>>> available to any jenkins job . . . does anyone have any recommendations >>>> for creating a library of methods and setting up jenkins to make the >>>> methods in it available to jenkins? Should they be static methods? NOT >>>> static? Any thoughts would be greatly appreciated. >>>> >>>> Oh! And does anyone have any advice on how to set up a dev environment >>>> to develop this sort of thing? I find it awkward to develop when I don't >>>> have access to all of the objects that would be available within a jenkins >>>> instance. >>>> >>>> I hope that makes sense. >>>> >>>> Thanks, >>>> Guy >>>> >>> >>> >> -- >> 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]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/CABnTgtWX4XPCjAxgbAkR9SYTU03%2BEKUiShjiEo9LzqRVNBsUdQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-users/CABnTgtWX4XPCjAxgbAkR9SYTU03%2BEKUiShjiEo9LzqRVNBsUdQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF3MyEtdjVvx3yKer%3D8PTJb1pjyTDwLen_OTXu4uLkkpQ%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF3MyEtdjVvx3yKer%3D8PTJb1pjyTDwLen_OTXu4uLkkpQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS5YgPgAGyExqFkfnJgpisRdBwY2PuA2vKU1tXrY115XSw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
