On 22.01.2016, at 14:14, ogondza <ogon...@gmail.com> wrote: > How about some criteria for testing? Requiring X% for code coverage is > clearly wrong. But how about the plugin needs to have _some_ tests? What I > believe we should do is having a CI that verifies the plugin selection > against the core version. Not sure we should use ATH or plugin-compat-tester > or both.
Looks like a reasonable requirement. Any idea how we could incorporate that? -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/74A77A96-3E33-4011-BA3D-E259EF2EE246%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
