On Tue, Aug 20, 2013 at 8:35 AM, Kevin Fleming (BLOOMBERG/ 731 LEXIN)
<[email protected]> wrote:
> The other recommendations you've received are really valuable, and you
> should not discount them. If you go down the route of downloading HPI/JPI
> files yourself, you will lose the benefit of dependency handling that
> Jenkins provides. You will have to download *all* necessary plugins (not
> just the top-level list you want to install), and when you want to upgrade
> any plugin you'll need to be sure that its depedencies are met and that it
> does not break dependencies for other plugins. This is all manageable, of
> course, but seems like a great deal of extra work when you can just use
> jenkins-cli to tell Jenkins 'install plugin XYZ' and let it handle that
> stuff.
But if your real concern is being able to spin up new jenkins
instances with your current set of plugins, you should be able to just
copy the hpi/jpi files out of a working jenkins's plugins directory
and drop into the new one - with some level of concern about matching
versions with the new jenkins core you are installing - but if you are
on the LTS track that doesn't change that often.
--
Les Mikesell
[email protected]
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
