Thanks for the pointer. TBH, I haven't thought much at all about what that 3rd bullet actually means :-) it was suggested by Johannes Schnatterer (and I don't know his email address, I hope he's reading this!) and it sounded like an area where this would be potentially relevant.
I can clearly see the value and trade-off of JenkinsPipelineUnit <https://github.com/jenkinsci/JenkinsPipelineUnit>. I think it's a great project. I suppose one path that Jenkinsfile Runner could take is not to stub out side effects. I think that's what Johannes meant by "integration" in "integration test" means. So that you can actually run some real stuff. But I'm also intrigued at the thought of Jenkinsfile Runner running Jenkins in it, while stubbing out actual steps. That can certainly enable some additional testing scenarios. The question I'd like to ask to people like Johannes, folks behind JenkinsPipelineUnit (once again I don't know their email addresse! even though I met them in Jenkins World!), and pipeline users in general is whether they find that valuable. On Thu, Mar 1, 2018 at 3:00 PM Jesse Glick <[email protected]> wrote: > 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. > -- Kohsuke Kawaguchi -- 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/CAN4CQ4xM944n7TqMiz9FGF913j9ewPa6SR0wsTK%2B1_aPNadR%2BA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
