denis256 notes and projects

Jenkins published the jenkins-2.570 release on June 23, 2026. This weekly release is not marked as a prerelease, and the most useful operator change is broader SSH key discovery for ECDSA and Ed25519 keys. It also cleans up several UI bugs around Build History, build logs, and dynamic form lists.

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

SSH key discovery covers modern defaults

The SSH change is small, but useful. Jenkins now searches for ECDSA and Ed25519 keys in default SSH key locations. That matters when a Jenkins process uses standard SSH client key paths and newer key types are already present.

The practical result is less path checking during setup. A credential or connection flow that depends on default key discovery should now behave closer to what users expect from common SSH tooling. The release notes do not describe a new setting or migration step, so treat this as a behavior cleanup rather than a config change.

This is the kind of fix that rarely looks large in a changelog. It still matters because SSH details usually fail at the worst time, during access setup or automation repair. Removing one more special case is good maintenance work.

Build views and dynamic lists get less brittle

Several fixes target day to day page behavior rather than core execution. The Add button is re enabled when a deleted hetero-list item should allow another item to be added.

These are form bugs, not scheduler changes. Still, they affect real administration work because dynamic lists appear in configuration screens where users add, remove, and adjust structured items. A button that stays disabled after an item is deleted can make a page look broken even when the underlying data model is fine.

Build related views get cleanup too. The Build History tooltip should no longer be clipped by hidden overflow, and the cancel button is restored on the build log page.

None of this changes job semantics. It does make the web UI less likely to interrupt routine checks. For operators who spend a lot of time in Build History and log pages, that is the right kind of boring fix.

Workspace text and Korean localization improve clarity

Workspace text file responses now include a UTF-8 charset. That is the kind of HTTP detail users notice only when it is wrong: text opens with odd characters, browser rendering differs, or tooling guesses the charset. Adding the charset makes the response more explicit for clients that care about encoding.

The release also expands Korean localization. The notes mention completed Korean translation for jenkins.management messages and added Korean text for the security configuration screens.

This is not just a cosmetic update for Korean speaking administrators. Security settings are places where unclear labels create real operational risk. Better localized text helps teams review settings without translating critical UI in their heads.

Where to get it

Use the linked release artifacts and notes for the exact build. For source context, use the project repository.

• Release page: Jenkins 2.570 release
• Repository: jenkinsci/jenkins
• Tag: jenkins-2.570