CloudBees Jenkins Enterprise 1.11.4

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-03-15

Based on Jenkins LTS2.107.1-cb-3

Rolling release Security release

New features

  • CloudBees Internal Ticket: [CJP-8385]

    Updated the default redirection of <cjedomain>/ to use the new user experience

Resolved issues

  • CloudBees Internal Ticket: [TIGER-4438]

    Fixed a compatibility issue with the new Jenkins 2.107.1 serialization restrictions.

  • CloudBees Internal Ticket: [TIGER-4363]

    [rhel][centos] Support bundle now lists only installed packages

  • CloudBees Internal Ticket: [TIGER-4297]

    [aws] Resolve an issue where, in some cases, the worker-remove operation would fail with Terraform error when removing an older worker

  • CloudBees Internal Ticket: [TIGER-4119]

    Resolve an issue where support bundle generation did not clean the temporal files which could result in filling the disk

  • CloudBees Internal Ticket: [TIGER-3126]

    Enhance the CLI so that elasticsearch-update operation should reject the configuration if the number of instances is less than the number of replicas + 1

  • CloudBees Internal Ticket: [TIGER-2973]

    Resolve an issue with customer supplied AMIs where sentinel files could be created but be not readable by non-root

  • CloudBees Internal Ticket: [TIGER-3193]

    When a CLI command fails, the command is no longer shown as this could disclose sensitive data such as passwords

  • CloudBees Internal Ticket: [TIGER-4402]

    The script can be used to update the hostname name used by a mesos-slave worker node. The hostname can change when a AWS instance is restarted (i.e. stop and start instance) and the mesos-slave is set to the public DNS name of the instance.

Usage: cje run repair-server WORKER_ID

Known issues

  • CloudBees Internal Ticket: [TIGER-4516]

    [aws][ubuntu] New instance types (m5, r5, etc.) using NVMe-based devices cannot be used as Master workers