On Fri, Jan 3, 2020 at 12:46 PM Lee Meador <
l...@leemeador.com> wrote:
> whoever wrote the script expected bundled plugins to be installed on startup unless a higher version was already installed. I don't know if that is true any more.
Yes, that sounds right.
> Then there is the fact that I don't know my way around the Jenkins code.
Plugin management code is rather complicated I am afraid, and
undocumented. If you have to dig into sources, start with
`PluginManager`.
> there is some code that lets you select and install plugins on first-time startup. It offers to install "suggested" plugins or it offers a list of plugins and installs versions it selects.
Yes, in the setup wizard. For OSS Jenkins this does nothing different
than just going to `/pluginManager/available`, selecting the same
plugins, and installing them without restart.
When the WAR includes bundled plugins, these get installed immediately
upon startup, before the setup wizard is even displayed. I think
CloudBees products actually use a custom proprietary component
(`cloudbees-installation-manager`) to do this, rather than the bundled
plugin system built into Jenkins core, but I do not know much about
the topic.
> I would like to know whether Jenkins still installs the bundled plugins on startup forcing a return to "official" versions every time.
It should only install bundled plugins during startup if they are not
yet installed, or are installed but in older versions.
I am not sure who defined the requirements for the project but I would
suggest just ignoring bundled plugins unless you have a specific
reason to deal with them and are ready to test various such scenarios.