On Sunday, February 19, 2023 at 7:32:47 PM UTC-7 Olivier Lamy wrote: On Mon, 20 Feb 2023 at 08:38, Mark Waite wrote: > > > > On Sunday, February 19, 2023 at 2:50:44 PM UTC-7 Olivier Lamy wrote: > On Mon, 20 Feb 2023 at 00:54, Mark Waite wrote: > > > > I like the idea. Would that have detected the specific problem that prompted the idea? Are there tests in plugins that depend on the API plugin that would have detected the issue? > > tbh not sure we will detect all possible issues :) but at least we > could prevent some. >
I think that we need more evidence that the technique would detect issues. I'm not sure how the api plugins are much different from other plugins that provide an API. The bouncycastle API plugin would lead to tests of 800+ plugins, with those plugins in various states of use (some with no installations, many with very few installations). It is clearly an API plugin. I am not sure that the work to test drive in 800 plugins is worth the benefit gained from that testing. I would expect most of the work in that effort would be preparing the consumer plugin to use the new release of the API plugin. The git client plugin provides the JGit API but is not an API plugin in the same way that pure API plugins are. It would lead to tests of 29 plugins, with the same issue that many of those plugins have very few installations and may not even compile with a new version of the git client plugin. I see many challenges to be addressed and am not yet persuaded of the number of cases that the technique will detect. -- 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/13f63083-b3bc-43df-be6c-beefa8295ec9n%40googlegroups.com.
