That's similar to what I've done in the past, Another approach would be to create an empty plugin project and add your scripts and plugin dependencies to that. Then you can use the jenkins unit test harness for writing your tests and hpi:run for manual testing.
/B On Sat, Jan 3, 2015 at 11:39 PM, Dylan Cali <[email protected]> wrote: > Ha, just as I post that I was able to get it to work by adding one > more dependency, javax.servlet-api. But the question still stands if > there's a more elegant way then the brute force approach I've gone > with. > > Thanks > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" 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-dev/CAM1XmN8UT9ht-fsu8hLJp9XUexVg2kidZYxGxCnXxB4K3W5MHw%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- Robert Sandell *Software Engineer* *CloudBees Inc.* -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/CALzHZS0o2UFOpuUOQ7zv5uzPzeAu%2BgkMpMM8NweYkoq3i4tAyQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
