For the third use case, what might be useful is an archetype or two analogous to
https://github.com/jenkinsci/archetypes/tree/master/scripted-pipeline/src/main/resources/archetype-resources https://github.com/jenkinsci/archetypes/tree/master/global-shared-library/src/main/resources/archetype-resources which use the Docker packaging and take care of all the boilerplate needed to have a Maven module which, when “built”, runs the specified `Jenkinsfile` or library against some test inputs in a well-controlled environment, and presumably passes or fails according to some conditions. (For example, Groovy validation scripts, akin to Maven Invoker?) I think the hard part would be stubbing out side effects you do not want—something handled easily by JenkinsPipelineUnit, at the cost of running in an unrealistic environment. For anyone interested in this general topic, https://issues.jenkins-ci.org/browse/JENKINS-33925 has some longstanding discussion and ideas. (And, wow, 85 votes! Alas there are no clear acceptance criteria for closing it.) -- 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/CANfRfr3fDig6_-X-Pjnm1jRgv3RFZnC59ezcVpuSsjU4Wrw9sQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
