Last checked and updated on 03 May 2026What Is New in Jenkins 2.452.x
| Category | Key Changes |
|---|---|
| Major Changes | People view removed, Debian package updates, recursive file copy improvements |
| UI Enhancements | Modernized progress bars, dropdown components, copy-to-clipboard button, computer icon legend |
| Security & Permissions | Agent/Provision permission in global security, Resource Root URL protection |
| Bug Fixes | Static agent configuration fixes, plugin extension discovery, restart handling |
| Infrastructure | Spring Framework upgrade, WebSocket proxy support, Java size reduction on Windows |
What major UI changes were introduced?
The most noticeable UI change is the complete removal of the People view from core Jenkins. This was a security-related decision that moves this functionality to a separate plugin. If you still need people management features, you'll need to install the People View plugin.
Several UI components got modernized including progress bars across various locations and new dropdown item components. The build console output now includes a convenient "copy to clipboard" button, and there's a new computer icon legend that clearly shows agent status - including a specific icon for agents that aren't accepting tasks.
How did agent management improve?
Agent configuration got several important fixes. The static inbound agent GUI configuration now properly handles the tunnel argument - it won't incorrectly include -tunnel with no argument when the field is left blank. This resolves issues with agent connection instructions.
For remote file operations, Jenkins now supports recursive file copy even when local and remote nodes have incompatible character sets at the binary level (like ISO-8859-1 and CP-1047). This eliminates many encoding-related transfer failures that previously required workarounds.
What security enhancements were added?
The Agent/Provision permission is now available in global Security configuration when using matrix-based authorization strategies. This gives administrators more granular control over who can manage agent provisioning.
Authenticated access to Resource Root URL has been prevented, closing a potential security vector. Proxy configuration also became more secure - the system won't configure an authenticator if the proxy username field is blank, avoiding potential misconfigurations.
What infrastructure updates should I know about?
The Spring Framework BOM was upgraded from 5.3.33 to 5.3.34, bringing various underlying improvements and fixes. For Windows installations, jlink is now used to reduce Java size, following the same optimization previously applied to Linux installations.
Debian packages now have specific temporary files for better Unix domain socket support and require Debian 10/Ubuntu 20.04 as minimum supported versions. The External Job Monitor gained Session ID support to avoid HTTP 503 responses during job monitoring.
What were the critical bug fixes?
A significant fix addresses plugin extension discovery when the variant plugin is installed alongside plugins with OptionalExtension - these extensions will now be properly discovered without requiring additional scans.
Restart behavior was improved across different operating systems. Jenkins won't attempt self-restart on OSes where this isn't supported, and a macOS-specific crash during restart was resolved. Non-Pipeline builds interrupted by controller restarts now properly show as aborted rather than failed.
FAQ
Do I need to do anything about the removed People view?
Yes - if you use the People view, install the People View plugin before upgrading to maintain this functionality. The core functionality was moved to a plugin for security reasons.
Will my existing agent configurations break after upgrade?
Probably not, but check your static inbound agent configurations. The tunnel argument handling was fixed, so if you had blank tunnel fields, they'll now work correctly instead of generating invalid commands.
What's the impact of the recursive file copy improvement?
This fixes transfers between nodes with different character encodings. If you move files between systems with incompatible encodings (like mainframe and Linux systems), these operations will now work without manual intervention.
Should I update my deployment scripts for the Debian changes?
If you use Debian packages, ensure your target systems meet the new minimum requirements (Debian 10/Ubuntu 20.04). The Unix domain socket support improves performance but doesn't require script changes.
How does the plugin extension discovery fix affect me?
If you use the variant plugin with other plugins that have optional extensions, those extensions will be available immediately instead of requiring a manual scan after plugin installation.