On Fri, Sep 29, 2017 at 4:23 PM, martinda <[email protected]> wrote: > Which type of test is good enough catch that the http_request plugin has > a transitive dependency on Guava 11.0.1. Guava 11.0.1 is currently provided > by the jenkins core, but this will change
ATH would probably catch that kind of thing. `JenkinsRule` would probably not, hence JENKINS-41827. > Which type of automated test approach should I use for my Jenkinsfiles > and my Pipeline libraries? I want to test against the exact line up of > Jenkins war version and plugin versions I use in production. I do not know that there is any single recommendation. Some people use JenkinsPipelineUnit, which is fast and lightweight but very low fidelity. Pipeline component plugins themselves rely heavily on `JenkinsRule`-based tests, which you could presumably use yourself to get higher fidelity (including Jenkins core and plugin versions) at the expense of more effort to mock out irrelevant parts of the environment. -- 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/CANfRfr3KrM%2BRZf5vQ_tLWHmN9rCG63DRi4gZGAdDy42%2BGE%2BdMg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
