Using the support for @Library seems like a much simpler way to go about
testing it, and was thought about as the option. We were hoping to have
turnaround time locally as well as having more codified tests. We have seen
the Groovy CPS plugin bite us in the ass a few times, so we wanted to get
There is no reason why you cannot automate the local running of the Jenkins
tests. See how plugin development works - they have setup to start a local
Jenkins instance with plugin installed, and it should be relatively simple
to automate that to run test jobs and check for output.
That said, y
