Last checked and updated on 03 May 2026What Is New in Jenkins 2.440.x
Jenkins 2.440.x LTS delivers a significant UI modernization, crucial security patches, and foundational changes to agent communication. This release focuses on phasing out legacy protocols and enhancing system monitoring.
| Category | Key Changes |
|---|---|
| Major Enhancements | People view removal, UI modernization, Debian package updates, Recursive file copy enhancement |
| Agent Communication | Deprecation of JNLP URL launch mode, WebSocket and tunnel support improvements |
| Security | Multiple security advisories addressed across sub-releases |
| Bug Fixes | Fixed folder icons, agent log customization, form validation issues |
| Deprecations | JNLP URL agent launch, inbound agent configuration options |
What major UI changes were introduced?
The most visible change is the removal of the built-in People view, which is now available as a separate plugin. The UI has been significantly modernized with updated progress bars, dropdown components, and a new "copy to clipboard" button for build console output.
Various interface elements including buttons, menus, and link designs have been refreshed to provide a more consistent and modern user experience. The build history page now shows parameter symbols for pending jobs, making it easier to identify parameterized builds at a glance.
How does agent communication change in this release?
This release accelerates the deprecation of traditional JNLP-based agent connections. The -jnlpUrl argument is now deprecated in favor of the more flexible -url and -name parameters combined with -webSocket or -tunnel options.
Configuration options for static inbound agents in the GUI, particularly the WebSocket field (deprecated since 2.440.x), now properly handle empty values instead of generating incorrect launch commands with empty tunnel arguments. The tunnel property for inbound agents in JCasC that was broken in 2.437 has been fixed, though it remains deprecated.
What security improvements should I be aware of?
Multiple security advisories were addressed across the 2.440.x sub-releases. The 2.440.2 release specifically included important security fixes alongside upgrades to Winstone 6.18 and Jetty 10.0.20, which address several CVEs including CVE-2023-44487.
Access to Resource Root URL is now properly restricted to prevent authenticated access, and the X-Content-Type-Options HTTP header has been added to agent listener responses to address false positives from security scanners.
How has disk space monitoring been improved?
Disk space monitoring has been completely reworked with configurable thresholds both globally and per agent. The system now provides better warnings when disk space is low and ensures agents are properly taken offline when thresholds are breached.
For Configuration as Code users, the diskSpaceMonitor configuration has been replaced with diskSpace. Existing configurations using the old format will display warning messages but continue to work, though migration to the new format is recommended.
What performance optimizations were implemented?
Significant performance improvements include restored artifact display performance when using remote artifact managers like S3, resolving a substantial slowdown introduced in version 2.394. The update also reduces high memory usage from XStream2.AssociatedConverterImpl and fixes thread creation issues that could occur under heavy load.
Build interruption handling has been improved - non-Pipeline builds interrupted by a controller restart are now marked as aborted rather than failed, providing more accurate build status information.
FAQ
Do I need to update my agent launch scripts immediately?
While the JNLP URL method is deprecated, it still works. However, you should plan to migrate to the new -url and -name parameters as the deprecated method will be removed in a future release.
What happens if I had the People view configured?
The built-in People view has been removed. You need to install the separate People View plugin from the update center to restore this functionality.
Replace any
diskSpaceMonitor entries in your configuration-as-code files with diskSpace. The functionality remains the same, but the configuration key has changed.
Are there any Java version requirements changes?
Jenkins 2.440.x continues to support Java 11, 17, and 21. However, note that container images without "jdk" in the tag now use Java 17 by default instead of Java 11.
What should I do about the WebSocket deprecated warning?
The WebSocket field in the inbound agent configuration is deprecated. Reset these options to defaults and use the command-line -webSocket option instead when launching agents.