Jesse - cheers for pointing out the previous AWS packaging attempt, I will take a look.
Re version pinning, if this can’t be done in the POM, are there any Jenkins tools which can do this, apart from the cloudbees assured update feed? (I’m thinking of how we could support users on Jenkins community edition.) Re what gets included - we could insist that any plugins included in a cloud vendor metapackage meet certain criteria, so that they can play together better: - They must be able to no-op if the user doesn’t need them (ie their default is to quietly sit on the Jenkins server and not do anything, until the user configures them). - They must all use the same cloud provider SDK artifact (probably the Jenkins re-packaged HPI version of the SDK). - If appropriate, they must all take their baseline configuration from the same cloud provider ‘global config’ plugin. Re pre-defined packages - I would certainly like to see the cloud vendors get more involved with supporting their respective Jenkins plugins. Chris -- 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/623C5041-5D06-47C9-BD2F-CA7336B7BC53%40chriskilding.com.
