-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some bundled plugins are ignored and not updated #282
Comments
It seems detached plugins are explicitly excluded from any lists - but I can't find any documentation to explain why: https://github.com/jenkinsci/plugin-installation-manager-tool/blob/master/plugin-management-library/src/main/java/io/jenkins/tools/pluginmanager/impl/PluginManager.java#L1469-L1474 |
Available updates only works on plugin files not the jenkins war itself so it won't be too useful here. Not sure if it's intentionally excluded, most likely just not implemented. |
Not sure I understand? I do not know whether it's possible to inspect the war to read the included versions and see if there's updates via the CLI (in general), but the updates definitely show up in the Jenkins Update Center, so there must be a way? I ran into this today. To solve it I added the deps that are normally bundled into the war into my |
I mean this CLI tool does not inspect your installed versions in any way, it just processes a
Yes that is the normal workflow |
Glad to know I'm not crazy 😂 This workflow does have the downside for the fully automated situations, where nobody ever looks into the Update Center - I was not even aware "detached plugins" are even a thing and I was very confused to not even see these via the Thanks for filling in the missing info 👍 I probably do not have the capacity to learn how to implement this, but I might look into updating the README or smth. |
Current Jenkins LTS version is 2.263.3. This version has a bouncycastle-api plugin bundled, version 2.16. However, latest version is 2.18. The Jenkins UI reveals this:
However, running plugin manager 2.5.0 (latest) doesn't update it:
Same happens with the
command-launcher
andjdk-tool
plugins, both bundled in the latest LTS.Later edit note: adding the plugin explicitly to the command line
i.e. via --plugins bouncecastle-api
will find the latest 2.18 version and download it. But the problem is that it doesn't detect the bundled version.The text was updated successfully, but these errors were encountered: