Hi, we were also wondering why there´s that pipeline-as-code approach available and strongly recommended everywhere - without any traditional support (automated tests) of developing clean code for it.
So we worked around that by doing the following: - we have a Test Jenkins instance running where the pipeline code is tested first. pushes or released versions only go to productive Jenkins if well tested - we "mocked" the pipeline DSL methods which enables us to at least do some basic groovy syntax and compilation tests. So far, Mockito, JUnit, Spock helps us a little. - we developed some simple "integration-test" pipelines where we can test the pipeline code first - before testing or using it with real-life projects. It´s currently a time-consuming and sometimes frustrating process to get things running - but we are looking forward to a lot of improvements coming soon. Good luck, Torsten -- 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/df090766-3ba2-4e19-af8f-a57b5f97256c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
