I agree with Jesse. The suite as is is so large already. The plugin-compat-test was made for purposes similar to this I believe, so why not use the tools that are available?
On Tue, Jun 4, 2019 at 11:29 AM Jesse Glick <[email protected]> wrote: > On Tue, Jun 4, 2019 at 1:23 PM Joseph P <[email protected]> wrote: > > we would avoid regressions that are related to configuration-as-code > > I think that should be handled differently, for example by something > like JENKINS-45047, or `plugin-compat-tester`, or > `buildPlugin.recommendedConfigurations()`, or Dependabot. There are > plenty of critical plugins which are prone to breaking due to changes > in core, and we cannot possibly stuff the core test suite full of all > of them. (In fact I would prefer to be _removing_ some plugins from > the `test` POM.) Instead, plugins define tests and a `jenkins.version` > known to pass them, and we use various tooling to ensure that these > tests are also run against newer dependency versions so that > regressions are caught in a timely manner. > > -- > 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/CANfRfr0ALHHvTcOeRRrmLV10B%3DaeODTGWsOcQ2yCWu4BKoT5dw%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- Website: http://earl-of-code.com -- 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/CAPiUgVduMQyrmKzkjyktOCHw8EhbzzOhMO6tAotZVSvO5cp8dw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
