CloudBees Jenkins Enterprise 1.8.0

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-07-19

Based on Jenkins LTS2.60.2-cb-1

Rolling release Security release

Security advisory * Security Advisory 2017-07-10

+ On July 7 2017, the security fixes described in the advisory were made available to CJE Managed Master and CJE Operations Center through an * incremental upgrade. These fixes are now included in this full release.

New features

  • CloudBees Internal Ticket: [TIGER-2635]

    With this enhancement, CJE would allow customers to use custom hosted zones that would enable better control for routing traffic inside a VPC.

  • CloudBees Internal Ticket: [TIGER-3157]

    When using Identity v3, either a domain id or a domain name must be provided when logging in. For some customers it may be easier to handle domain name directly because domain id is a uuid that is not user-facing.

  • CloudBees Internal Ticket: [TIGER-3206]

    Disable terraform version check to avoid installation or upgrade delays in "firewalled" environments

  • CloudBees Internal Ticket: [TIGER-2874]

    Add support for ipv6 ingress on AWS.

  • CloudBees Internal Ticket: [TIGER-3014]

    This fix makes it easier for users to pull logs from specific docker containers and add it to a support bundle, if required.

  • CloudBees Internal Ticket: [TIGER-2535]

    Improve docker cleanup. It is now based on spotify/docker-gc that optimizes the removal of tagged docker images.

  • CloudBees Internal Ticket: [TIGER-1952]

    Preliminary support of self-signed certificates has been implemented. Full support requires an upgrade of master-provisioning plugins which will be available later.

Resolved issues

  • CloudBees Internal Ticket: [TIGER-3207]

    This fix improves the reliability of NFS checks while installing a CJE cluster with an NFS storage backend

  • CloudBees Internal Ticket: [TIGER-3162]

    The cje check operation can be run to ensure a CJE cluster has been installed correctly. This ticket fixes an issue that caused the operation to fail.

  • CloudBees Internal Ticket: [TIGER-3201]

    Handles index restore failures during elasticsearch-restore operation more gracefully. If an index restore fails, it will be skipped but it won’t prevent other indexes to be restored.

  • CloudBees Internal Ticket: [TIGER-3255]

    Fixed typo in cluster-init input file.

  • CloudBees Internal Ticket: [TIGER-3196]

    Logstash was not sending logs to ElasticSearch after a RedHat Enterprise Linux or CentOS upgrade. This change resolves this issue.

  • CloudBees Internal Ticket: [TIGER-3240]

    The list-resources operation wasn’t displaying newly added Workers if the internal=yes config was set in the cluster-init.config file.

Known issues

  • CloudBees Internal Ticket: [TIGER-3319]

    CJE, when installed using NFS 4.x servers as a storage solution, will not properly mount JENKINS_HOME in containers used by CJE. This issue could lead to installation failures. This issue only applies to installations on OpenStack and vSphere.

Before starting an install or upgrade using an NFS 4.x server, please contact your CloudBees support representative for details on how to adjust the configuration to ensure that it works properly.

The CloudBees team will provide the resolution to this issue in the upcoming release

  • CloudBees Internal Ticket: [TIGER-2321]

    A CJE Admin can change the JNLP port on the Operations Center UI, however, this is not a best practice as this is set dynamically by CJE on startup.

  • 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-2459]

    The alert There was an error reporting analytics data links to an invalid URL within the cluster. You can access this by selecting the Manage Jenkins link on the left side of the page.

  • CloudBees Internal Ticket: [TIGER-2692]

    The list-resources operation does not work on OpenStack.

  • 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).

To workaround, and recover in a different availability zone, you will need manually edit the .dna/project.config file and update the availability_zone property for each machine instance prior to starting the recovery operation.

  • CloudBees Internal Ticket: [TIGER-3278]

    With the i3 family of EC2 computes, the instance_storage type is not being leveraged by CJE