CloudBees Jenkins Enterprise 1.11.2

CloudBees will no longer be supporting CloudBees Jenkins Enterprise 1.x after July 30, 2020. This end-of-life announcement allows CloudBees to focus on driving new technology and product innovation for CloudBees CI. For information on moving to CloudBees CI, please refer to CloudBees Jenkins Enterprise 1.x to CloudBees CI on modern cloud platforms migration guide which has been created to help you with the migration process. Existing customers can also contact their CSM to help ensure a smooth transition.

RELEASED: Public: 2018-01-17

Based on Jenkins LTS2.89.3-cb-1

Rolling release Security release

Security advisory * CloudBees Internal Ticket: TIGER-4097

+ CJE 1.11.2 has updated VM OS images (AMIs and OVAs) that integrate the security patches from OS vendors.

New installations of CJE that use these new images will get the patches automatically.

If you have an existing CJE deployment, you should update your CJE deployment to ensure that new machine instances get these patched OS images. After updating CJE, you should also follow these instructions to patch the existing images:

New features

  • CloudBees Internal Ticket: [TIGER-3520]

    CJE Support Bundle now includes the output of the cje status command

Resolved issues

  • CloudBees Internal Ticket: [TIGER-4107]

    Simplify Managed Master/Operations Center containers' lifecycle management

  • CloudBees Internal Ticket: [TIGER-4051]

    [anywhere] / [nfs] NFS mount problems have been observed in some environments since the docker images for Managed Master and Operations Center is based on the Alpine Linux distribution.

For these cases, a new operation nfs-update allows to modify NFS mount options, in particular to specify and explicit nfs version to use. NFS locking issue in cloudbees/cje-oc:2.89.1.7 due Alpine version change. We suggest protocol version 3.

  • CloudBees Internal Ticket: [TIGER-4032]

    Prevent Castle from triggering a snapshot creation while another one is still pending

  • CloudBees Internal Ticket: [TIGER-3987]

    Remove JVM incompatible flags automatically when upgrading

  • CloudBees Internal Ticket: [TIGER-3950]

    Fixed issue where a NullPointerException occur while editing the Managed Master configuration UI

  • CloudBees Internal Ticket: [TIGER-2973]

    Fixed issue where some installation files were not readable by a non-root user

  • CloudBees Internal Ticket: [TIGER-3999]

    Fix translation of no_proxy parameter to the java system property http.nonProxyHosts.

When specifying example.com in no_proxy, it results into example.com and *.example.com being added to the http.nonProxyHosts system property to have a matching behaviour.

Known issues

  • CloudBees Internal Ticket: [TIGER-2355]

    If a docker image is not found during master provisioning, the user is not given any indication of the error

  • CloudBees Internal Ticket: [TIGER-2371]

    OneShot agents don’t support pipeline resumption

  • CloudBees Internal Ticket: [TIGER-2426]

    Unable to execute jobs from Managed Master on CJE Worker

  • CloudBees Internal Ticket: [TIGER-2522]

    Masters go offline during Operations Center upgrade

  • CloudBees Internal Ticket: [TIGER-2724]

    Deleting a Managed Master from Operations Center does not actually delete it

  • CloudBees Internal Ticket: [TIGER-2427]

    cluster-recover fails if subnet is created on another availability zone

  • CloudBees Internal Ticket: [TIGER-3539]

    [aws] In some cases, destroying a cluster will hang on the S3 bucket deletion. A workaround is to manually delete the S3 bucket, then apply the operation again

  • CloudBees Internal Ticket: [TIGER-3739]

    It is not possible to remove workers when Operations Center is down

  • CloudBees Internal Ticket: [TIGER-3957]

    [anywhere] Cluster destroy does not remove /etc/.*_installed files