CloudBees Jenkins Enterprise 1.10.0

4 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: 2017-11-08

Based on Jenkins LTS2.73.3-cb-1

Rolling release Security release

New features

  • CloudBees Internal Ticket: [TIGER-3722]

    [aws] It is now possible to encrypt EBS volumes for Jenkins Homes by providing a key at init time.

  • CloudBees Internal Ticket: [TIGER-3692]

    The elasticsearch-update operation now offers recommended values.

  • CloudBees Internal Ticket: [TIGER-3582]

    The boto3 and botocore libraries used by the underlying dna tool have been updated respectively to 1.4.7 and 1.7.10.

  • CloudBees Internal Ticket: [TIGER-3563]

    Docker daemon options can now be provided at init time.

Resolved issues

  • CloudBees Internal Ticket: [TIGER-3760]

    With CJE [anywhere] the operation credentials-update was missing the input file to change cjoc credentials.

  • CloudBees Internal Ticket: [TIGER-3740]

    [anywhere] Installation will now fail fast if duplicate ips are entered for workers or controllers.

  • CloudBees Internal Ticket: [TIGER-3702]

    Fixed an issue causing space-separated args in dna run .. commands to fail

  • CloudBees Internal Ticket: [TIGER-3699]

    Fixed a condition causing docker cleanup process to get into a faulty state

  • CloudBees Internal Ticket: [TIGER-3689]

    [anywhere] Fix network interface detection in Palace in cases where there is no network interface named eth0.

  • CloudBees Internal Ticket: [TIGER-3686]

    [centos/rhel] Make sure idmapd service is started, as it is required to use NFS v4 or later.

  • CloudBees Internal Ticket: [TIGER-3622]

    [anywhere] Clarify logging during pre-check

  • CloudBees Internal Ticket: [TIGER-3621]

    Elasticsearch is now started before Operations Center during installation, which prevents some transient errors seen in Operations Center.

  • CloudBees Internal Ticket: [TIGER-3597]

    When running CJE on [aws] additional tags specified through resource_tags are now applied as well to EBS volumes and snapshots.

  • CloudBees Internal Ticket: [TIGER-3593]

    Fixed a problem that occurred occasionally where the Setup Wizard does not display when creating a master.

  • CloudBees Internal Ticket: [TIGER-3592]

    Mesos executor timeout has been raised to 10 minutes (from 5 minutes). This should prevent agent provisioning failures in case of big docker images to be pulled.

  • CloudBees Internal Ticket: [TIGER-3540]

    Fix router logs (/var/log/router/*) rotation on controllers. This will reduce the overall size of support bundles and reduce the risk of running out of disk in some instances.

Known issues

  • CloudBees Internal Ticket: [TIGER-2355]

    If you enter an invalid Managed Master image location under the Manage Jenkins page on Operations Center, when deploying the new instance, the log window will only show that it’s attempting to deploy and will not give any further feedback. Correct the image location to resolve this.

  • CloudBees Internal Ticket: [TIGER-2371]

    CJE allows you to enable using one-shot executors. These provide slightly faster provisioning of the executors. However, the current implementation of one-shot executors doesn’t support pipeline resumption.

  • CloudBees Internal Ticket: [TIGER-2426]

    CJE doesn’t support installing the Palace Cloud Plugin into masters that are not managed by CloudBees Jenkins Enterprise.

  • CloudBees Internal Ticket: [TIGER-2522]

    Managed Masters may appear to be not accessible when Operations Center is being upgraded. This issue occurs when the internal application router is being updated and is a temporary condition.

  • CloudBees Internal Ticket: [TIGER-2724]

    When deleting a Managed Master, the data associated with the master is retained in a backup snapshot used for recovery purposes. If you add a new master with the same name, it will recover the data from the snapshot and re-create it.

  • CloudBees Internal Ticket: [TIGER-2427]

    A CJE cluster-recover fails if its subnet is created in another availability zone. When using the operation cluster-recover, it is simpler to keep the cluster in the same AWS availability zone (AZ).

  • CloudBees Internal Ticket: [TIGER-3414]

    CJE can fail to upgrade when a worker was incompletely set up.

Under some circumstances, a cje prepare worker-add operation can fail. The typical case (on Amazon) is when the user’s MFA code is incorrectly entered when prompted after the "apply" step. This results in a worker that is incompletely set up and the instance isn’t started.

When this condition exists, an upgrade will fail.

To resolve this, use the cje prepare worker-remove on the partially created workers, and then restart the upgrade process.

  • CloudBees Internal Ticket: [TIGER-3539]

    Under some circumstances, an unexpected file prevents the operation cluster-destroy from completing on AWS.

When destroying a cluster, CJE can also delete the S3 buckets, but a file docker.tar.gz may be present in the bucket which prevents CJE from finishing. To work around this issue, manually delete the file using the aws CLI and apply the cje operation again.

  • CloudBees Internal Ticket: [TIGER-3739]

    If Operations Center is not running, you will be unable to use the cli to remove workers. If a worker configuration is damaged, Operations Center won’t start properly. In the event of this situation, please contact CloudBees customer support for assistance in resolving this.

  • CloudBees Internal Ticket: [TIGER-3641]

    IPv4 forwarding must be enabled on the machine and VM instances used to host CJE.