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.
AWS & Azure users may see a warning about expired licenses at first CJP boot: this message can be safely ignored and will be removed once the setup process is completed.
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.
Shared Docker Cloud Configuration is not supported in the 2.7.20.x release line.
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.
Especially for large clusters with multiple CJE instances, automatic backups of CloudBees Jenkins Analytics can cause high memory usage. The workaround when this happens is to disable automatic backups of Analytics.
The Move/Copy/Promote feature does not work correctly when the UI auto-refresh option is enabled. It is recommended to disable auto-refresh.
CloudBees Jenkins Analytics does not fully support the Pipeline job type. This can compromise the accuracy of the statistics, because some of the information coming from pipelines will be missing.
Jenkins supports the definition of complex labels for nodes, including expressions with logic operators and conjunctions. This level of complexity is not currently supported by CloudBees Jenkins Analytics, so labels having complex expressions are not being reported correctly. As a workaround, it is possible to simplify node label expressions by defining multiple labels for the same node.
When running CJOC on Windows, deleting a client master from CJOC may display an error indicating that a file could not be deleted. The workaround is to stop CJOC and manually delete the client master folder.
The Embedded Elasticsearch validation button does not work correctly in this release. To check instance availability, access any Analytics dashboard in the CJOC. Dashboard data populates after a short lag time.
The Dismiss button for the Analytics administrative monitor always redirects to a 404 error page.
Shared Slaves and Shared Clouds permissions may be missing from the RBAC permission matrix. If so, navigate to the "New Item" wizard, and then go back to the permission configuration page.
Once Analytics data backup is reconfigured, the CJOC instance needs to be restarted in order for Analytics to start the new backup cycle and apply the specified timeout period.
Analytics logs may show some upload failures in the 2.7.20.x line. The issue is currently being investigated.
A connection failure error is reported if Analytics Dashboard Creator is accessed via a URL where the CJOC hostname/ip is different from the one configured in the Jenkins Global Configuration page.
If jobs use label operators to restrict the agent labels they can run on, those logic operators are displayed in the Analytics Dashboards as if they were labels themselves.
The process computing the clock difference between CJOC and the client masters takes too long, which results in multiple Cancellation Exceptions in the CJOC logs.
The Analytics BulkReindexOp doesn't appear among the cluster operations options. The workaround is to restart Jenkins.
JNLP Shared Cloud cannot be renamed after creation. You must delete and then recreate it with the new name.
The Dumb Slaves "Launch Method" drop down duplicates the option "Launch Slave Agent via web start." Any of the two options have the same effect, choosing one or the other will not affect the behavior.
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.
If upgrading from a Jenkins instance with Analytics version prior to 1.8.100, the Analytics Unreadable Data Monitor may be showing unresolvable data warnings. These can be ignored and dismissed.
The copy of a client master is not supported, and should not be performed. Doing so may result in undefined behaviour.
The client master's Move/Copy/Promote operations bar freezes showing an
invalid path error message if the client master is in a 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).
If a build agent from either a Shared Slave or a Shared Cloud is returned to CJOC while CJOC is in certain specific points during the shutdown lifecycle, then the connected master will no longer retain a record of the lease and the record of the lease return will not have been persisted on CJOC. The specific build agent in question will be unavailable for lease until the build agent lease is manually force released.
When you are moving a client master, it will be disconnected and reconnected. Move operation of many masters may fail because some of them will get reconnected during the move.
If Windows Installer requires an action confirmation by Windows UAT System (e.g. on Windows 7), the UAT Window shows incorrect application name. There is no security impact in this issue.
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.
Shared Cloud instances on CJOC are malfunctional if their names contain spaces and other special symbols. The recommended symbol set is a-zA-Z0-9-_
This version is available here