Jenkins 2.570 - SSH Keys and Workspace Text Encoding

Jenkins 2.570 was published on June 23, 2026, with a compact set of fixes for operators who use Jenkins around data platform builds, batch jobs, and deployment pipelines. The most useful change is SSH key discovery: Jenkins now searches the default ECDSA and Ed25519 key locations, which reduces one common source of brittle agent or remote access setup.

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

Jenkins now searches for ECDSA and Ed25519 keys in the default SSH key locations. That is a small change, but it matters when data jobs clone private repos, fetch dbt packages, pull schema definitions, or push generated artifacts through SSH. Many operators have moved away from RSA keys. When the automation layer only looks in older paths, builds fail before any useful pipeline logic starts.

The release notes do not describe a new config flag or a migration step for this behavior. Treat it as a compatibility improvement in key discovery. If your controller or agent images already mount explicit credentials into Jenkins, this should not change that model. If you rely on default home directory key files, this release makes ECDSA and Ed25519 less likely to require local glue.

Workspace text file responses now include the UTF-8 charset. This is relevant for web processing and ETL teams that inspect generated manifests, CSV samples, JSON extracts, or logs through Jenkins during a failure. Without a charset, browsers and intermediate tools can guess. That guess is usually invisible until a non ASCII value in a source file, country name, customer field, or test fixture renders incorrectly.

This is not a storage format change in the release notes. It is an HTTP response detail for workspace text files. The practical result is clearer behavior at the edge where Jenkins serves build artifacts or temporary files for humans and tools to inspect. Teams that parse workspace files through the Jenkins UI should still treat the workspace as build output, not as a durable data store.

Several changes are UI repairs, but a few touch operational paths that matter during incident work. The cancel button is restored on the build log page. The Add button is re enabled when a hetero list item is deleted. The hetero list keydown handler gets its missing event parameter back.

These are not data pipeline features. They are control plane fixes. That distinction matters. When a Jenkins job backs an ingestion run, a schema test, or a batch publish step, broken controls waste operator time at exactly the wrong moment. Restoring cancel behavior on the build log page is especially relevant for long running jobs that need a clean stop path from the page already showing the failure.

The build history tooltip clipping fix and chevron alignment fix are visual, but they still sit near a common operations workflow: reading recent job state. The release also includes Korean translation work for jenkins.management messages and security configuration screens. For global platform teams, better localized admin text can reduce ambiguity around management screens, even if it does not change runtime behavior.

The notes also mention a smaller experimental UI details bar padding change. That is mostly product maintenance. It does not imply any change to queue semantics, pipeline syntax, credential storage, REST behavior, or job execution based on the release notes.

This release is not marked as a prerelease, and the notes do not call out breaking changes. Operators should still test it against jobs that depend on SSH key defaults and jobs where people open workspace files from the browser. Those are the two areas where small behavior changes can surface quickly in a data platform environment.

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