This used to be done for pipeline with the 'workflow-aggregator' plugin, afaik it's not very popular though? and isn't really being maintained anymore
Any one able to provide any background? Or why this would be a good / bad idea Thanks Tim On Fri, 21 Feb 2020 at 14:50, Chris Kilding <[email protected]> wrote: > Hi Rick, > > For specific use cases, perhaps we are looking more at meta-plugins than > metapackages… > > Meta-plugins would consist (almost) exclusively of a POM. Versions of each > downstream plugin that is relevant to the use case would be pinned and > controlled in the POM. Each meta-plugin release marks a combination of > those plugins that are certified to work together. This takes the version > testing and pinning work out of the Jenkins admin’s hands. > > The various cloud providers are good candidates for meta-plugins, because > every integration with a provider is typically built on the following > foundational components: > - An SDK (e.g. aws-java-sdk-plugin) > - A shared configuration mechanism (e.g. aws-global-configuration-plugin) > > And the cloud providers update their SDKs frequently, especially with > security fixes, so the rate of dependency churn is high. > > > On the topic of advertising popular plugins, platform-plugins.json looks > like a good in-band mechanism of doing this, and if particular use case > meta-plugins are popular, they too should be advertised through it. > > Chris > > > On 21 Feb 2020, at 00:58, Rick <[email protected]> wrote: > > > > Hi Chris, > > > > Thanks for providing the advice. People usually use Jenkins as one or > several specific scenes. Like you mentioned an AWS metapackage. I think we > can define two kinds of metapackages. One is the pre-defined which likes > AWS use cases, e.g. Another kind is that show the popular metapackages > which come from the users of Jenkins distribution customise service. How do > think about this? > > > > Platform-plugins.json is a good example. Thanks Jesse! > > > > Best regards, > > Rick > > > >> On 21 Feb 2020, at 00:33, Jesse Glick <[email protected]> wrote: > >> > >> On Thu, Feb 20, 2020 at 9:51 AM Chris Kilding > >> <[email protected]> wrote: > >>> These metapackages in turn could be consumed (and featured) by the > proposed Jenkins customise service. > >> > >> Also > >> > >> > https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/jenkins/install/platform-plugins.json > >> > >> -- > >> 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/CANfRfr2-mR6ShssSHEHL-f8msytS4_x6K%3DFSmaYBF6kju4gj%2Bg%40mail.gmail.com > . > > > > -- > > 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/F10030E1-760D-48BD-B149-7B8595596ABC%40126.com > . > > -- > 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/0371C77F-E9D3-48B1-BD77-D5B0C1173F90%40chriskilding.com > . > -- 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/CAH-3Bic3nxaJM4hGB2jWr70%2BG2AgCenjdLaCoo60E3dNynkekQ%40mail.gmail.com.
