CloudBees Jenkins Platform

RELEASED: Public: 2017-03-02

Based on Jenkins LTS2.32.2

Rolling release

New features


Resolved issues

  • CloudBees Internal Ticket: CJP-6315

    In some cases, when upgrading from, Beekeeper shows an error message.

Known issues

  • CloudBees Internal Ticket: OSS-1350

    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

  • CloudBees Internal Ticket: OSS-1074

    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

  • CloudBees Internal Ticket: CJP-5556

    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

  • CloudBees Internal Ticket: CJP-5528

    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

  • CloudBees Internal Ticket: CJP-5508

    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

  • CloudBees Internal Ticket: CJP-5487

    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

  • CloudBees Internal Ticket: CJP-5479

    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 Client Master with CJOC without specifying the custom update center in a first step. Then, when done, configure the custom update center

  • CloudBees Internal Ticket: CJP-5232

    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.

  • CloudBees Internal Ticket: CJP-4979

    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

  • CloudBees Internal Ticket: CJP-4920

    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

  • CloudBees Internal Ticket: CJP-3832

    When running both CJE and CJOC on the same Windows instance, in certain circumstances HA can incorrectly prevent the instance from starting. Running CJE and CJOC on the same instance is not a recommended setup for a production instance.