2.19.4 (2016-11-23)

2.19.4 (2016-11-23)

- Reduce logging level when the localization resource is missing ResourceBundleUtil#getBundle(). (issue 39604)
- Custom remoting enable/disable settings were not properly persisted on the disk and then reloaded. If the option has been configured in Jenkins starting from 2.16, a reconfiguration may be required. (issue 39465)
- Prevent NullPointerException when rendering CauseOfInterruption.UserInterruption in build summary pages for non-existent users. (issue 38721 and issue 37282, regression in 2.14)
- Display transient actions for labels. (issue 38651)
- Performance: Fix the performance of file compress/uncompress operations over the remoting channel. (issue 38640, issue 38814)
- Add user to restart log message for restart after plugin installation. (issue 38615)
- Remoting 2.62.2: Improve connection stability by turning on Socket Keep-alive by default. Keep-alive can be disabled via the -noKeepAlive option on slave agent process. (issue 38539)
- Remoting 2.62.2: Prevent NullPointerException in Engine#connect() when host or port parameters are null or empty. (issue 37539)
- Jenkins startup does not fail if one of ComputerListeners throws exception in the onOnline() handler. (issue 38487)
- Fix handling of the jenkins.model.Jenkins.slaveAgentPort system property, which was not honored. (issue 38187, regression in 2.0)
- Properly enable submit button on New Item page when choosing item type first. (issue 36539)
- Add missing internationalization support to ResourceBundleUtil. It fixes internationalization in Blue Ocean and Jenkins Design Language. (issue 35845)
- Properly handle quotes and other special symbols in item names during form validation. (issue 31871)
- Prevent deadlocks during modification of node executor numbers (e.g. during deletion of nodes). (issue 31768)
- Restore automatic line wrapping in Build Step text boxes with syntax highlighting. (issue 27367)
- Print warnings if none of Tool Installers can be used during the tool installation. (issue 26940)
- Node build history page was hammering the performance of the Jenkins instance by spawning parallel heavy requests. Now the information is being loaded sequentially. (issue 23244)
- Fix JS/browser memory leak on Jenkins dashboard. (issue 10912)

https://jenkins.io/changelog-stable/#v2.19.4