Upgraded Email-ext Plugin from
Upgraded Matrix Authorization Strategy Plugin from
Upgraded CloudBees Role-Based Access Control Plugin from
Upgraded Script Security Plugin from
Fixes the security issues described in the advisory.
Credentials Binding plugin does not work if Git plugin is not installed. The workaround is to install the Git plugin.
JENKINS-37545 - Dependencies to plugins which were previously bundled on Jenkins WAR (detached plugins) are not resolved automatically. These plugins will have to be manually installed.
When renaming a folder, if clicking "Apply" instead of "Save", a confirmation pop-up dialog is shown with duplicated header and footer. The workaround is to use the "Save" button.
When configuring the license on the setup wizard, a forbidden error may be displayed if the
Back button is clicked. If stuck in this situation, the
Retry button will help to go back to the license configuration page.
CloudBees Registration plugin (and any plugin that depends on it), CloudBees Deployer plugin and CloudBees Back-up Cloud plugin are deprecated and can cause the Jenkins instance not to start up correctly. They should be removed/uninstalled.
When a client master is straight deleted from a CJOC, the connection details are left behind. The workaround is to delete the CJOC connection details from the client master global configuration page.
A second promotion of a job to a target instance which does not have RBAC configuration can fail with
no replication permission. The workaround is to enable RBAC on the target instance or use groovy to remove the RBAC configuration from the promoted job.
It's possible to see a warning about an invalid license if PSE or cloud foundry plugins are installed but the instance has a regular EE (Enterprise-Edition) license. To remove the warning it's necessary to disable/uninstall the offending plugins.
At the very first startup, relocating a pipeline job may not work correctly due to the Move/Copy/Promote pipeline handler not being fully registered. Restarting the instance will solve the issue.
There is a timing issue when connecting a Client Master to a CJOC for the first time, using a custom update center. The recommended workaround is to associate the CM with CJOC without specifying the custom update center in a first step. Then, when done, configure the custom update center.
CloudBees License Plugin must be updated to version 7.16+ to avoid an issue with Client Master license refresh failing.
The Move/Copy/Promote feature does not work correctly when the UI auto-refresh option is enabled. It is recommended to disable auto-refresh.
When pushing connection details from CJOC to a clean CJE (along with SSO), the user gets logged in the client master as "admin" rather than as the user who started the configuration in CJOC. The workaround is to logout and login again.
When CJOC is enforcing the Role Based Access Control authorization strategy on client masters, the Groups detail screens on client masters will include two "Inherited from Jenkins" sections. The top-most section refers to the current master (which is a "Jenkins" but should be referred to as the connected master name shown in the breadcrumb bar) and the lowest "Inherited from Jenkins" section refers to CJOC (which is a "Jenkins"). The visual display of the information is less confusing when the masters have been organized using folders on CJOC as then the two "Inherited from Jenkins" sections are visually separated by the folders
GitHub Branch Source plugin may fail to load if an old version of cloudbees-github-pull-requests-plugin is pinned. The solution is to unpin it and update it to the last version.
When updating CJE from a previous version to 2.7.19.x, CloudBees Pipeline Stage View Extensions plugin and CloudBees Pipeline Template plugin may fail to load at first Jenkins startup. A second restart is needed to make the plugins work.
The client master's Move/Copy/Promote operations bar freezes showing an
invalid path error message if the client master is in disconnected state. Workaround is either to wait for the client master to reconnect or, if the connection is broken, to release the client master from CJOC (in this case the local Move/Copy/Promote operation will work).
When using a custom update center the "Check now" button throws a signature error, however the functionality works as expected.
When running both CJOC and CJE on the same Windows instance, in certain circumstances HA can incorrectly prevent the instance from starting. (Running CJOC and CJE on the same instance is not a recommended setup for a production instance)
This version is available here