On Thu, Aug 29, 2019 at 10:33 AM Gavin <[email protected]> wrote: > it means a plugin doesn't work the same on newer versions
Possibly, but much more commonly it just means some _test_ does not work the same on newer versions of Jenkins, sometimes for pretty minor technical reasons. Yes that ought to get fixed, but there is no rush. The problem with changing the library configuration in “YOLO mode” is that somebody (especially not the plugin maintainer) files a PR, it gets a test failure, and they waste half a day trying to figure out what they did wrong…before figuring out that there is nothing wrong with the PR at all, `master` builds would be broken the same way if there were any, and the apparent regression is coming from some change to another repository no one was even paying attention to. Then somebody then needs to drop whatever they were doing and get the plugin’s `master` build fixed. Using Dependabot would let us avoid this kind of problem, while still guiding maintainers toward testing against the latest and greatest in a timely manner. (You would get an automated PR proposing to test against a new LTS, or more generally proposing to use a new version of the library; in the normal case that the build passes, you would merge it; if not, you would track down the issue as soon as you have time to focus on it; `master` would stay blue, barring infrastructure problems.) There is not yet any Dependabot support for Jenkins libraries, however, so we would need to do some groundwork first. -- 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/CANfRfr356LBgMQaHOdi1at4fKeiaTq_5Wt36h2e0o9qg2T8Lpg%40mail.gmail.com.
