On Sun, Feb 19, 2023 at 4:50 PM Olivier Lamy <[email protected]> wrote:
> I'm not quite sure how to implement this technically because > downstream plugins may use the api-plugin as direct dependency with > version or using the bom so this means we would have to inject an > incremental bom or change version. > https://issues.jenkins.io/browse/JENKINS-45047 gives the basic idea. The basic machinery is already used from `jenkinsci/bom`. See the second bullet point in https://github.com/jenkinsci/maven-hpi-plugin/pull/66#issuecomment-1110203758 for discussion. how to detect all downstream plugins? As Mark mentions, that would rarely be practical. We could test some *representative* downstream plugins. A different approach would be to make the UC generator continue to pluck the latest version from Artifactory for “long-tail” plugins, but for plugins managed in `bom`, pick up their versions from the last stable `master` build or whatever. That would ensure that regressions among a large set of commonplace plugins do not accidentally slip onto the UC before they are corrected. This would not have helped in this case, though, since `kubernetes` has a very specialized test suite that is not covered by `bom`. Similarly for `artifact-manager-s3` vs. AWS SDK, etc. -- 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/CANfRfr1sk28k%2B-gVMuiHHAp2EuynnEXw8cP%3DMVFpt1D-PAD8ZQ%40mail.gmail.com.
