On Thu, Feb 21, 2019 at 8:43 AM Oleg Nenashev <[email protected]> wrote: > I propose to focus on development tools
Since the primary use case is offering updates to plugin repositories, I would suggest including at least one example of `*-plugin`. The question is which dependencies ought to be eligible for upgrade. I do not think we want to update Jenkins core or plugin dependencies gratuitously, since this would limit availability of new releases with only modest productivity gain: more realistic functional tests, less distance from `master` to whatever `plugin-compat-tester` would use. Definitely we can freely upgrade the parent POM. I would be happy for such updates to be auto-merged in fact, so long as the build passes obviously. > pre-1.0 projects only Or just plugins that (a) have fairly low installation count, (b) are maintained by people actively participating in the trial. > More repositories can be added if somebody is interested to participate in > the Dependabot evaluation. Sign me up! I _do_ need to make sure I get notifications of these PRs in Octobox.io, if they are not simply automerged. Merely watching a repository is not enough—GH has autosubscribed me to hundreds of repos, and the resulting thousands of notifications go to /dev/null. Maybe Dependabot can be configured to request me as a reviewer? -- 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/CANfRfr2pcB-%2BGsnJFKO7sR3drv3F43ADqqwAW0RU_bJUrpKEuw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
