denis256 notes and projects

Jenkins jenkins-2.572 was published on July 7, 2026 as a regular weekly release, not a prerelease. The most important change for administrators is tighter deserialization behavior in core, with new limits around PersistedList, COWL, and Object fields.

The full release notes and downloads are on the GitHub release page.

Deserialization defaults get tighter

Two entries in this Jenkins release are about how core handles stored data during deserialization. The release restricts elements in PersistedList and COWL, and it prohibits deserialization of Object fields by default.

That is not a UI feature, but it is the kind of core change operators should notice. Jenkins instances often carry a long history of job configuration, plugin state, node records, and persisted admin choices. Narrower deserialization rules reduce the amount of loosely typed data that core will accept without an explicit model.

The notes do not call this a breaking change, and they do not list a manual migration step. Still, this is worth reading before a busy controller upgrade. If a local plugin or internal extension stores broad Object fields, the safer assumption is that it should be checked against this release rather than found during a production restart.

Password policy gets an extension point

The release adds a password complexity rule extension point through JENKINS 69789. This matters most for Jenkins installations that still use local Jenkins accounts or mix local accounts with external identity systems.

The useful part is where the policy can live. Instead of treating password rules as only a process document, plugin authors and platform teams get a core extension point for rule logic. That is cleaner than relying on side checks that users only meet after a failed audit.

The release notes do not define a default policy in this changelog draft. They name the extension point. For operators, the practical takeaway is to watch the plugin ecosystem and internal Jenkins extensions for adoption of that new hook.

Manage Jenkins gives Nodes more room

Jenkins 2.572 includes a targeted change for the newer Manage Jenkins experience. The Nodes page is made wide in the experimental Manage Jenkins UI.

That sounds minor until the controller has many agents. Dense node data needs width. For operators managing a larger Jenkins setup, forcing that view into a narrow layout makes the page harder to scan and easier to misread.

Modal dialogs and Plugin Manager links

The bug fixes in this release are narrow and practical. Modal dialogs now stay fixed to the viewport. That should make dialogs less awkward on long pages or pages with scroll heavy content.

The Plugin Manager also gets a fix for links when a plugin has no wiki URL. This is the kind of paper cut that tends to show up during upgrades, plugin audits, or cleanup work. A missing legacy wiki value should not make the link behavior worse than it needs to be.

Neither fix changes how Jenkins jobs run. Both reduce admin friction in places where operators are already doing maintenance work. That is still useful, because maintenance pages are where small UI defects waste real time.

Where to get it

• Release page: Jenkins 2.572 on GitHub
• Project repo: jenkinsci/jenkins
• Tag: jenkins-2.572