CloudBees Accelerator 11.1 Release Notes

As of version 11.1, perpetual license files include a Version field and are therefore no longer transferable to succeeding product versions. At run time, to be considered valid by the Cluster Manager, the license file must have a Version that equals or exceeds the version of the Cluster Manager itself. Version checks consider only the major.minor version (for example, a license for 11.1 is valid for 11.1.0, 11.1.1, 11.1.2, and so on).

eMake authenticates with the Cluster Manager via the eMake/Cluster Manager protocol version to ensure that the eMake and Cluster Manager licenses match. If the license has no Version field, it will be considered invalid by the 11.1 Cluster Manager.

You can upgrade to new patch releases (but not new feature releases) without acquiring a new license. For example, if your current license specifies 11.1 , then you can use a Cluster Manager with version 11.1 , 11.1.1 , 11.1.2 , and so on. Also, for example, if your license specifies 12.0 , then you can use a Cluster Manager with version 12.0 , 12.0.1 , 12.0.2 , and so on, as well as 11.x .

The Administration > Licenses page in the Cluster Manager web UI now has a Version column, which provides the product version of each license in the list. This information is blank for a license with no explicit version (such as an evaluation license).

Make sure that you import a compliant license into the Cluster Manager before upgrading. For assistance, see https://support.cloudbees.com/ . For details about importing a license, see the “Importing Your License” section in the “Configuring CloudBees Accelerator” chapter of the CloudBees Accelerator Installation and Configuration Guide , available in the CloudBees Accelerator documentation . (EC-13170 and EC-13154)

Accelerator now supports Google Cloud Platform (GCP) on Linux platforms. This integration lets you configure the Cluster Manager to use GCP to spin up agents on demand. (EC-13242)

Accelerator now supports Azure Cloud Provider (Azure) on Linux platforms. This integration lets you configure the Cluster Manager to use Azure to spin up agents on demand. (EC-13240)

For Amazon EC2, the ability to choose to use the IAM role of the server as credentials is introduced on Linux platforms. (EC-12710). For details about this enhancement, see the CloudBees Accelerator {accelerator-product-version-11-1} Help , available in the CloudBees Accelerator documentation .

TLS-based authentication and encryption is now available for communication between eMake and agents on Linux platforms. For details about configuring TLS, see the “Configuring TLS” section in the “Configuring CloudBees Accelerator” chapter of the CloudBees Accelerator {accelerator-product-version-11-1} Installation and Configuration Guide , available in the CloudBees Accelerator documentation . For a list of the eMake command-line options for using TLS for builds, see the “List of eMake Command-Line Options” section in the “Electric Make Basics” chapter of the CloudBees Accelerator {accelerator-product-version-11-1} Electric Make User Guide . (EC-13267)

You can now configure an agent AMI that you use for cloud bursting to automatically scale the number of agents according to the number of CPUs on the host. This facilitates using this single image as a template across many different instance types, regardless of the CPU count on each type, to get the ideal number of agents. For details, see the “Enabling Automatic Scaling of the Number of Agents in the Agent AMI” section in the “Configuring CloudBees Accelerator” chapter of the CloudBees Accelerator {accelerator-product-version-11-1} Installation and Configuration Guide , available in the CloudBees Accelerator documentation . (EC-13270)

The --emake-job-timeout eMake option is introduced. This option is especially useful for adding resiliency to the eMake “test case” mode. It specifies the number of seconds to allow a job to run before timing out, after which it terminates the job and discards all job output. For details, see the “List of eMake Command-Line Options” section in the “eMake Basics” chapter of the CloudBees Accelerator Electric Make User Guide , available in the CloudBees Accelerator documentation . (EC-13043)

This release provides better performance and greater compatibility for Android builds as follows.

The Visual Studio integration (which is bundled with Accelerator) is upgraded to version 5.3.0. This version contains a number of updates.

Among these updates, the VS IDE extension uses CloudBees Accelerator Electrify to build rather than ecdevenv, so there are extensive changes to the settings dialog and the behavior of the build. Differences include the following:

For a detailed list of new features and resolved issues in version 5.3.0, see the “What’s New” section in the CloudBees Accelerator 5.3.0 Visual Studio Integration Guide , available in the CloudBees Accelerator documentation .

ElectricInsight (which is bundled with Accelerator) is upgraded to version 5.5.1 and is rebranded to CloudBees Accelerator Insight (”Insight”). The 32- and 64-bit executables for Insight are installed.

Insight is licensed separately from Accelerator. An Insight license file is required to run reports. All other functionality (view-only mode) is available without a license.

For the list of new features and resolved issues, see the CloudBees Accelerator Insight 5.5.1 Release Notes , available in the CloudBees Accelerator documentation . For information about the 32- and 64-bit executables for Insight and about using Insight, see the CloudBees Accelerator Insight 5.5 User Guide , available in the CloudBees Accelerator documentation .

The following Cluster Manager web server security-related issues are fixed:

Affected systems might encounter reduced performance on both ext3 and ext4 file systems. Symptoms might include

To help determine if this issue exists, run the dmesg | grep hung_task_timeout command. hung_task_timeout errors show that this issue is present. Contact your kernel provider for another version of the precompiled kernel.

You should consider upgrading to 2.6.32-131 (RHEL 6.1) or downgrading to 2.6.18-194.32 (RHEL 5.5).