I have two clarification questions regarding ATH, JenkinsRule and plugin-compat-tester.
Q1: 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 with https://github.com/jenkinsci/maven-plugin/pull/102 Q2: 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. On IRC the suggestion was to create a custom update center containing only the plugin versions I find in production, and run my code using the ATH. There is a chicken and egg problem there to get the UC up, but I can live with it. Thanks, Martin -- 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/ec84ea88-9b8a-4b65-b049-3c64fb6df90a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
