Looking for 5 Jenkins admins to test an upgrade-risk scanner

Using Jenkins Showing Off
,
1

I’m building a tool that checks Jenkins core, Java and plugin versions for potential upgrade risks. I’m looking for Jenkins administrators willing to try it and tell me where the report is useful - or wrong.

It takes a plugin:version list; no controller access or credentials are needed. The scanner is available to test for free. I’m also exploring a paid upgrade-rehearsal service, but this request is for feedback on the scanner.

Would anyone who recently upgraded Jenkins, or is planning an upgrade, be willing to try it?

2

Is your tool OpenSource? If no, I can not test it in my organization.

3

Hi,

The repository is public, so you can inspect the code, but I haven’t added a license yet, so it’s not formally open source at this stage. Do you mainly want to review the analysis logic or run it locally?

4 
def output = Jenkins.get().pluginManager.plugins.collect { p ->
    [id: p.shortName, version: p.version]
}
output.each { println "${it.id}:${it.version}" }

My use case is very peculiar, I have a 12 custom plugin variant and I’m alway running later version from jenkins and not LTS. I need to test on some other customer installation.

5

Thanks—that’s useful context. Custom plugin variants and weekly Jenkins releases are limitations of the current scanner: it uses public plugin metadata and an LTS upgrade target, so it can’t reliably assess your custom builds.

If you’re able to test it on a customer installation with their permission, I’d really appreciate feedback on which findings are useful, misleading, or missing. No controller access or credentials are needed—just the Jenkins version, Java version, and plugin versions.