On Tue, Jun 21, 2016 at 5:56 PM, Mark Waite <[email protected]> wrote: > I could search the plugin tree for JGit references to see the > actual scope of the problem.
I would start there, especially if you have a complete list of exhaustive members you could search for usages of. It would be very helpful if someone (hint hint Andres) were to routinely run `plugin-compat-tester` against all (@jenkinsci) trunk plugins with trunk dependencies, so we would at least find any regressions promptly. Also perhaps someone could resurrect Sorcerer and get it running on the @jenkinsci code base so we could quickly find method usages, even when they are of generic-sounding names like `release`. -- 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/CANfRfr24PiF6Lyp1VF75DpQgnreCWLvoRNdzv8YErw8cyOJWSA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
