I've been looking at the problem of jenkins plugins, and they seem to fit the custom package provider model vs a set of exec scripts in a module.
It's possible to get a list of versioned plugins that are present, and tell the system to install new ones, either from a source string, or a version (built from a URL), or central list of the plugins. The major problem I see is that it requires a java jar to do it. That would really need a set of variables from the module to connect & authenticate, and make sure that the jar is in the right place. Not to mention that java is installed. FYI: The old model - the direct download of the file - is in rtyler-jenkins & doesn't handle dependencies. By using the internal jenkins call to do the install, it will handle the dependency issues. If there's a good way to get variables to the provider plugin / or a templated script from the catalog then I can update to a provider. I intended to use the gem.rb as a base, since it's farily similar in concept and design. Thoughts? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
