A large part of automating a jenkins setup is dealing with the plugins. This is currently a pain.
The easiest solution would be to offload the dependency management to a package system that already deals with that. Native (rpm, deb, ...) would be a good solution for this.
A couple approaches are possible here:
- Use your existing ci infra and fpm packages after building/releasing
- Use your existing ci infra and add native packages support to the maven:hpi helper.
- Create / Provide jenkins jobs that package everything in the update center.
Possibly, if there was an api for the plugins, automation tools could integrate with that instead.
Related tickets on the puppet side: https://github.com/voxpupuli/puppet-jenkins/issues/841