Jesse I've been doing some work on the plugin installation manager cli tool. Right now, I'm trying to figure out whether the code in it that deals with bundled plugins is doing what it should. The requirement for that project said to just do what the install plugins script from the Docker distribution does.
What the script does is to care about the version of the bundled plugin if it would be needed by the dependencies listed in some requested plugin. Bundled plugins are treated identical to an installed plugin while figuring out dependency plugins and their versions. So if a dependency plugin has a min required version greater than the bundled (or installed) plugin, it will replaced with the greater min version when the script runs. In essence, bundled plugins are treated just like installed plugins in this way. That suggests to me that 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. Then there is the fact that I don't know my way around the Jenkins code. I suspect that the Jenkins UI for managing plugins has rules to decide which versions to offer and such. I have no idea how to find that code. I have no knowledge about whether or not it takes bundled plugins into account. Maybe it doesn't when offering but does when loading dependency plugins. Similarly, 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. Since I typically install the Cloudbees' version and it's been a while since I installed an OSS version, I don't know if that is a part of Jenkins OSS or not. If it's in OSS, I don't know where the code is. If only Cloudbees, I don't know how that feature would interact with what the plugin installation manager cli tool is trying to do. And I don't know how the Jenkins OSS group interacts with Cloudbees in regard to this sort of thing. I don't actually know if I need to know that. Does that give you some idea about what kind of info I'm looking for? If I only get one question answered, I would like to know whether Jenkins still installs the bundled plugins on startup forcing a return to "official" versions every time. -- Lee On Thu, Jan 2, 2020 at 9:13 PM Jesse Glick <[email protected]> wrote: > On Thu, Jan 2, 2020 at 5:46 PM Lee Meador <[email protected]> wrote: > > Release wars from the Jenkins OSS project don't seem to have bundles > plugins. Release wars from Cloudbees do. > > Yes, CloudBees products use bundled plugins; OSS Jenkins releases do > not (as of 2.x). > > The WAR packager tool can add bundled plugins, which is mainly handy > for running integration tests without needing to bother with > installing plugins at the start of a test. > > For the most part you can ignore the plugin bundling system, I think. > (It is unclear from your message how you got onto the subject.) > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0qqbRRVUch30uyBwhM4T6Sehtbq9q2dVWW1yTUMCkLaw%40mail.gmail.com > . > -- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAA4vtDQ_hqPDDLvc1c%3DapnbOAOYk7RngHSnzL0VNksQGWxkhmw%40mail.gmail.com.
