Jenkins 2.570 Release: SSH Key Discovery and Workspace UTF-8 Encoding

Jenkins 2.570 shipped on June 23, 2026 as a stable weekly release, not a prerelease candidate. The headline change for platform operators is pull request 26954, which extends SSH key discovery to ECDSA and Ed25519 keys in default key locations. That closes a gap for controllers and agents that rely on modern key types instead of legacy RSA only setups.

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

Pull request 26954 fixes key lookup so Jenkins searches default SSH key locations for ECDSA and Ed25519 material. Teams that moved agent authentication or Git checkout credentials to Ed25519 or ECDSA keys often saw silent failures when the controller could not locate keys the OpenSSH client would find on its own. The fix aligns Jenkins key resolution with standard ~/.ssh layout expectations.

For data engineering pipelines that trigger remote steps over SSH, this matters at connection time. A missing key type blocks checkout, artifact push, or remote script execution before any job logic runs. Operators who standardized on Ed25519 for shorter keys and faster handshakes no longer need workarounds such as forcing RSA key paths in job configuration. The tradeoff is unchanged: key permissions and credential binding in Jenkins still govern access; this release only fixes discovery, not authorization policy.

Workspace Text File Encoding ¶

Pull request 26912 adds charset UTF 8 to workspace text file responses. When jobs read configuration files, CSV extracts, or log fragments through the workspace browser API, clients previously received responses without an explicit charset. Browsers and HTTP clients could misinterpret multibyte content, which shows up as mojibake in pipeline artifacts or broken downstream parsing.

Batch and ETL style jobs that stage delimited files or JSON lines in the workspace depend on predictable encoding when operators inspect files through the UI or when lightweight scripts fetch workspace content over HTTP. Setting UTF 8 on those responses removes ambiguity for non ASCII data. Pipelines that assume Latin 1 or a locale specific default should still set encoding in their own transform steps; this change standardizes the controller response header, not file content on disk.

Several fixes target operational friction on active job pages. Pull request 26637 restores the cancel button on the build log page, which operators use to stop runaway or stuck executions without opening a separate API call. Losing that control during a long running extract or deploy step forces a harder kill path through the process tree or agent restart.

Hetero list widgets, common in plugin driven job configuration screens, receive two corrections. Pull request 26937 re enables the Add button after a hetero list item is deleted, so dynamic parameter blocks can be rebuilt without a full page reload. Pull request 26966 fixes a missing event parameter in the hetero list keydown handler, which could leave keyboard navigation in a broken state on dense configuration forms. These are UI layer fixes, but they reduce misconfiguration risk when teams edit parameterized pipeline definitions under time pressure.

The remaining items are mostly cosmetic or locale specific. Pull request 26972 reduces padding on the experimental UI details bar. Pull requests 26554, 26522, and related entries fix build history tooltip clipping, chevron alignment, and overflow layout on the Build History view. Pull requests 26955 and 26960 complete Korean translations for management and security configuration messages.

None of these alter scheduling, queue semantics, or agent protocol behavior. Teams running headless controllers with minimal UI interaction can treat this block as low priority unless they use the experimental interface or Korean locale packs.