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.
