I would prefer two types of solutions:
* pre-defined packaging. For example, AWS suite * the provider needs to guarantee the quality of it and maintain it. * users defined * we don’t guarantee anything about the suite. For example compatible something. We only provide the packing result How about this? Do you think it makes sense? On 02/21/2020 23:46，Jesse Glick<jgl...@cloudbees.com> wrote： On Fri, Feb 21, 2020 at 9:50 AM Chris Kilding <chris+jenk...@chriskilding.com> wrote: 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. This would not accomplish your goal, since plugin dependencies are on _minimum_ versions. A new release of one of the component plugins (say, `aws-java-sdk`) would be delivered to update sites immediately, regardless of what the current metaplugin POM says. This is why CloudBees offers https://docs.cloudbees.com/docs/admin-resources/latest/assurance-program/ as a value-add feature: the general update site publishes the latest Maven release of every plugin without any cross-testing. As for `workflow-aggregator`, I discourage its use since it just pulls in various stuff without any clear criteria for what is relevant and important. You might fare better with a pack which “supports AWS”, but you would still need to think about which parts of AWS are important for most users and which are not. BTW for an abandoned attempt in this area which I think was not mentioned previously: https://github.com/jenkins-infra/evergreen/tree/140e2a12da772917529fb93a9e48c2c34daec1c0/distribution/flavors/aws-ec2-cloud -- 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/CANfRfr3YQsE50L%2BqTnKqYFMyDrDSYbRNr_FWjFEsKZ6mK1C6Uw%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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/58e7c4ca.7c7e.1706fefa9c4.Coremail.zxjlwt%40126.com.
