Upgraded Jenkins baseline from
Upgraded CloudBees License Manager from 8.1 to 9.2
Upgraded CloudBees AWS CLI Plugin from 1.5.5 to 1.5.6
Upgraded CloudBees Amazon Web Services Deploy Engine Plugin from 1.15 to 1.17
Upgraded CloudBees Pipeline: Groovy Checkpoint Plugin from 2.3 to 2.4
Upgraded CloudBees Pipeline: Templates Plugin from 2.4 to 2.5
Upgraded CloudBees Skip Next Build Plugin from 3.8 to 4.0
Upgraded CloudBees Backup Plugin from 3.30 to 3.31
Upgraded Operations Center Analytics Reporter Plugin from 18.104.22.168 to 22.214.171.124
Upgraded Operations Center Client Plugin from 126.96.36.199 to 188.8.131.52
Upgraded Operations Center Cloud Plugin from 184.108.40.206 to 220.127.116.11
Upgraded Operations Center Agent Plugin from 18.104.22.168 to 22.214.171.124
Upgraded Operations Center Analytics Configuration from 126.96.36.199 to 188.8.131.52
Upgraded Operations Center Context Plugin from 184.108.40.206 to 220.127.116.11
Upgraded Bitbucket Branch Source Plugin from 1.2 to 1.8
Upgraded GitHub Plugin from 1.19.1 to 1.22.3
Upgraded Amazon Web Services SDK library from 1.10.50 to 1.11.37
Upgraded Bouncy Castle API Plugin from 1.648.3 to 2.16.0
Upgraded Branch API Plugin from 1.11 to 1.11.1
Upgraded Credentials Plugin from 2.1.4 to 2.1.6
Upgraded Docker Commons Plugin from 1.4.0 to 1.5
Upgraded CloudBees Docker Pipeline Plugin from 1.8 to 1.9.1
Upgraded Email-ext plugin from 2.45 to 2.51
Upgraded JUnit Plugin from 1.18 to 1.19
Upgraded LDAP Plugin from 1.12 to 1.13
Upgraded Mailer Plugin from 1.17 to 1.18
Upgraded Mercurial Plugin from 1.56 to 1.57
Upgraded Monitoring Plugin from 1.59.0 to 1.62.0
Upgraded Pipeline Input Step Plugin from 2.1 to 2.3
Upgraded Script Security Plugin from 1.23 to 1.24
Upgraded Support Core Plugin from 2.32 to 2.33
Upgraded Token Macro Plugin from 1.12.1 to 2.0
Upgraded Pipeline Graph Analysis Plugin from 1.1 to 1.2
Upgraded Pipeline API Plugin from 2.4 to 2.5
Upgraded Pipeline Groovy Plugin from 2.17 to 2.21
Upgraded Pipeline Job Plugin from 2.6 to 2.8
Upgraded Pipeline Supporting APIs Plugin from 2.8 to 2.10
Possible livelock in Operation Center Server that could leave the connection with a client master in a blocked state.
Fix a bug with sub-optimal big-O performance on abusive parallels
Credentials Binding plugin does not work if Git plugin is not installed. The workaround is to install the Git plugin.
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.
Solved the issue with the
Check Now button which was displaying a signature error for custom update centers.
Race condition when using a custom marker file on an organization folder could result in branch projects being created in the wrong repository folder, leading to numerous errors and anomalous behavior.
[MCP] infinite loop when browse.js
fetchFolders function goes to error
Unable to login with
remember me option at Client Master on CJOC
Exception while loading BitBucket Branch Source Plugin
Welcome to Jenkins 2 (upgrade banner) shown when upgrading
Client Master connectivity logs icon is missed in the UI
CloudBees Backup Plugin allows uploading files bigger than 5Gb to Amazon S3
CloudBees Backup Plugin allows resume during upload to Amazon S3
Improved error handling on CloudBees Backup Plugin when a file cannot be read
JNLP agents fail to connect when using nginx as a reverse proxy. Workaround is to upgrade to Operations Center Agent Plugin to 18.104.22.168 or higher
When upgrading from a previous CJE 2.x version with Beekeeper disabled, some optional dependencies of required plugins may not be correctly upgraded, causing issues after the upgrade. As a workaround, it is recommended to enable Beekeeper before performing an upgrade from a previous version.
Dependencies to plugins which were previously bundled on Jenkins WAR (detached plugins) are not resolved automatically. These plugins will have to be manually installed. More information JENKINS-37545.
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
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, go to
/login and log-in.
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.
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 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.
For non-existent users, the build summary pages can throw an exception (
NullPointerException) for user-interrupted builds (