CloudBees Jenkins Enterprise 1.7.1

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-06-28

Based on Jenkins LTS2.60.1

Rolling release

New features

  • CloudBees Internal Ticket: [TIGER-2698]

    CJE was updated to use OpenJDK 8u131. It now uses the CloudBees’s recommended Java parameters by default for its internal components, including the G1 garbage collector.

Existing installations should apply the new options to existing masters on an as needed basis.

  • CloudBees Internal Ticket: [TIGER-1802]

    This change makes CJE more secure, in that it further tightens the access controls provided to the docker containers running on the CJE cluster.

  • CloudBees Internal Ticket: [TIGER-2998]

    On AWS, CJE now supports Elastic Network Adapter (ENA) instance types.

  • CloudBees Internal Ticket: [tiger-2703]

    CJE now supports mount options for NFS.

Resolved issues

  • CloudBees Internal Ticket: [TIGER-3196]

    On Red Hat Enterprise Linux and CentOS installations, logstash did not send logs to ElasticSearch. This fix corrects this situation for new installations. Please contact support if you encounter this issue with an existing installation.

  • CloudBees Internal Ticket: [TIGER-2940]

    Under some circumstances, cluster recovery fails on a CJE anywhere installation. This change addresses these issues.

  • CloudBees Internal Ticket: [TIGER-3115]

    Upgrading from 1.6.3 to 1.7.0 required manual steps to complete the upgrade. This change automates those steps.

  • CloudBees Internal Ticket: [TIGER-2945]

    On AWS, after moving a task from one instance to another, various I/O errors can occur, or the volumes of a task can appear mounted multiple times. This change resolves these issues.

  • CloudBees Internal Ticket: [tiger-2543]

    When the cluster health was poor, CJE may take more time than necessary to generate the support bundle . This change allows the support bundle to be created more quickly under those conditions.

  • CloudBees Internal Ticket: [TIGER-3145]

    Under some circumstances, a failure occurs when attempting to produce a support bundle. This change detects the condition and records it.

  • CloudBees Internal Ticket: [TIGER-3110]

    Prior to this fix, creating a support bundle generated an error if firewalld was not running on CentOS or Red Hat Enterprise Linux.

  • CloudBees Internal Ticket: [TIGER-2939]

    During installation, a key request to reports a failure. This change resolves this failure.

Known issues

  • 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, then 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 will not be accessible when Operations Center is being upgraded.

  • CloudBees Internal Ticket: [TIGER-2022]

    Manually stopping a worker instance using AWS are unable to re-join the cluster when restarted. You should use the cje prepare worker-* operations to change the state of worker instances.

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