CloudBees Jenkins Enterprise 1.7.0

3 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-06-02

Based on Jenkins LTS2.46.3

New features

  • CloudBees Internal Ticket: [TIGER-2180]

    Now includes iPerf3 for network bandwidth checks.

  • CloudBees Internal Ticket: [TIGER-2207]

    Reduce the number of ELBs needed by CloudBees Jenkins Enterprise

  • CloudBees Internal Ticket: [TIGER-2549]

    A new operation docker-registry-update has been added to change the Docker registry after CloudBees Jenkins Enterprise has been installed.

  • CloudBees Internal Ticket: [TIGER-2780]

    CloudBees Jenkins Enterprise now allows configuration of AWS ELB in public subnets and instances in private subnets.

  • CloudBees Internal Ticket: [TIGER-2283]

    An additional security group can now be provided when using user-provided VPC. It will be applied to allow instances in the cluster.

Resolved issues

  • CloudBees Internal Ticket: [TIGER-3006]

    When cluster is recovered ensure that it is recovered in same AZ as it was originally running.

  • CloudBees Internal Ticket: [TIGER-3000]

    Ensure that S3FS mount of ES snapshot directory works when using AWS keys as credentials.

  • CloudBees Internal Ticket: [TIGER-2988]

    Fix the default instance size when calling worker-add to use the same as specified during cluster init.

  • CloudBees Internal Ticket: [TIGER-2963]

    Fix problem that caused IsManagedMasterFilter to fail in cluster operations with Operations Center

  • CloudBees Internal Ticket: [TIGER-3018]

    Cluster-recovery documentation now properly explains how to recover a destroyed cluster.

  • CloudBees Internal Ticket: [TIGER-2128]

    Significantly reduce size of OpenStack images.

  • CloudBees Internal Ticket: [TIGER-2677]

    RHEL users upgrading from 1.6.0 will have to provide Red Hat Subscription Manager credentials through registration-update operation.

  • CloudBees Internal Ticket: [TIGER-2648]

    CJE now properly enables "EBS-Optimized" machine instances both when installing the cluster and when adding new workers.

Known issues

  • Security Advisory 2017-06-06

    Security Advisory related to the favorite plugin. If you are using this plugin, please follow the instructions in the Security Advisory to get the fix.

  • CloudBees Internal Ticket: [TIGER-2321]

    A CJE Admin can change the JNLP port on the CJOC 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]

    CloudBees Jenkins Enterprise 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]

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

  • CloudBees Internal Ticket: [TIGER-2427]

    When using the operation cluster-recover, it is simpler to keep the cluster in the same AWS availability zone (AZ)

  • 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 properly on OpenStack.

  • CloudBees Internal Ticket: [TIGER-2522]

    Managed Masters will not be accessible when Operations Center is being upgraded.

  • CloudBees Internal Ticket: [tiger-3054]

    If log files are created rapidly, it is possible to fill local disk space before moved or purged.

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