CloudBees Jenkins Enterprise 1.11.3

2 minute read
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-02-14

Based on Jenkins LTS2.89.4-cb-3

Rolling release Security release

Security advisory * Security Advisory 2018-02-14

+ Fixes the security issues described in the advisory.

New features

  • CloudBees Internal Ticket: [TIGER-4148]

    [aws] Add support for eu-west-3 region

  • CloudBees Internal Ticket: [TIGER-4147]

    [aws] Add support for new AWS instance types (c5.*, m5.* …​) using nvme devices to mount EBS volumes.

Known issue : When using the Ubuntu distribution, this feature is unfortunately not yet working.

  • CloudBees Internal Ticket: [TIGER-4227]

    cjoc-update operation now allows specifying Jenkins command-line arguments

Resolved issues

  • CloudBees Internal Ticket: [TIGER-4170]

    Fixed an issue causing certificates signed by a custom CA not be imported into the Java certificates bundle

  • CloudBees Internal Ticket: [TIGER-4174]

    [aws] Update S3FS to 1.8.3 to add support for SSE-KMS

  • CloudBees Internal Ticket: [TIGER-4212]

    Fix an error issued after resizing the terminal

  • CloudBees Internal Ticket: [TIGER-4209]

    Fix a timeout issue during cje upgrade execution while waiting for Operations Center to come back online.

  • CloudBees Internal Ticket: [TIGER-4203]

    Fixed an issue while generating the support bundle causing it to hang with yum lock messages

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 operation does not remove /etc/.*_installed files.