Jenkins core shipped 2.589 this week and closed out seven commits on master, 41 files changed, 1830 insertions, 279 deletions. The headline items are a batch conversion of Groovy configuration views to Jelly, plugin support in the experimental job UI builds list, and a fix for plugin manager search under JENKINS-70822. None of it is flashy, but two of the three matter for anyone who customizes global configuration screens.
The 2.589 release cycle ¶
The release bot tagged jenkins-2.589 on November 3 and immediately flipped pom.xml back to development for 2.590. The diff is small and mechanical: the revision moves to 2.590, the changelist goes back to -SNAPSHOT, and the SCM tag resets to ${scmTag}. Two commits touched pom.xml in the window, which is just the release pair doing its normal job.
If you run LTS with plugins that pin against core APIs, note that project.build.outputTimestamp advanced again. Reproducible build verification against 2.590 snapshots will differ until the next stable point.
Six more Groovy views converted to Jelly ¶
The biggest technical commit of the week is the conversion of six Groovy configuration views to Jelly. This continues a long running effort across the core codebase. The affected views map cleanly to security and model configuration surfaces:
hudson/security/GlobalSecurityConfiguration(index view) plus its Java controllerhudson/security/csrf/GlobalCrumbIssuerConfigurationconfig view and controllerjenkins/model/ArtifactManagerConfigurationjenkins/mvn/GlobalMavenConfigjenkins/security/QueueItemAuthenticatorConfigurationhudson/views/ViewsTabBar/GlobalConfigurationImpl
Why care? Groovy views have historically been the source of XSS findings in Jenkins because of implicit HTML escaping differences. Jelly views go through l:layout and explicit escaping helpers, so every Groovy view removed shrinks that audit surface. Winners are plugin developers who now have a consistent template model to copy from. Losers are nobody, unless a plugin overrides one of these views and relied on Groovy side effects.
If you maintain a plugin with global configuration, this is the pattern to follow: convert your own .groovy views to .jelly before someone files a security hardening issue against you.
Plugin manager search gets a real fix ¶
JENKINS-70822 improves plugin manager search. Anyone who has typed a partial plugin name into the available tab and watched relevant results fall below garbage knows the pain here. The commit also touched hudson/Functions.java, which suggests shared rendering helpers were adjusted along the way.
For operators, this is a small but daily quality of life change. Plugin discovery drives actual security behavior: when an advisory lands, admins search for the affected plugin and update it. A search that hides the plugin you need gets you to patch later, not sooner.
Experimental job UI gains plugin support in the builds list ¶
The builds list in the experimental job UI now supports plugins. Related commits adjusted the jenkins.model.details rendering paths, including CauseDetail, DurationDetail, and the base Detail class, plus HistoryWidget.java. That matters because the modern builds detail rendering is where plugins hook in build metadata.
This is the experimental UI catching up to what plugins expect from the classic one. If you have JENKINS-70822 style extension points or custom build details, they will start appearing in the new builds list instead of silently vanishing. The tradeoff: plugin authors get another surface to test against, and behavior differences between classic and experimental views remain for a while.
CI and test harness housekeeping ¶
The remaining commits are plumbing. A CI build fix arrived right after the October security release, and renovate bumped the acceptance test harness Docker tag to v6787. The ATH bump is worth a glance if you run ATH based plugin tests locally; a newer harness image can shift flaky test results in either direction.
What to watch ¶
- The Groovy to Jelly conversion is clearly a rolling campaign. Expect more security and model configuration views next; if you override any of them, budget test time each release.
- The experimental job UI builds list now honors plugin details. Try your custom
Detailextensions there before the feature goes default. - 2.590 is already open for development. If this week’s security release cadence holds, expect the next batch of core changes to lean toward view hardening rather than API surface change.