CloudBees Build Acceleration v12.1

In this release the Cluster Manager is updated to use Apache 2.4.48, PHP 7.4.23, and OpenSSL 1.1.1l.

This release extends Android support to include builds based on AOSP 12 (EC-14110). For best results, users should regenerate their history files by running a full build with the --emake-history=create option; subsequent builds can be run without that option or with the value set to merge. Additional fixes for AOSP include:

This release also includes enhancements to Bitbake and Yocto support to expand compatibility and improve preformance. The changes include:

A bug in the C++ normalizing hash was preventing eMake’s jobcache functionality from detecting changes in source files which contained a C-style ending comment delimiter with more than one asterisk (e.g., **/).

Previously, eMake did not handle targets which were marked both intermediate and phony properly, resulting in build failures where this occurred. The most common way this would arise is with the use of a .SECONDARY: special target. This was preventing eMake from building the Linux kernel version 5.x (resulting in either hangs or with file-not-found build errors depending on the target architecture).

Improper locking of registry annotations and update operations were causing intermittent eMake aborts, resulting in incomplete builds.

Previously, eMake did not set these environment variables (when either stdout or stderr, respectively, is a tty). These are now set as appropriate.

The graph in the Cluster Manager’s Build Status > Performance > Agent utilization was showing fractional values on the y-axis.

An XFS file system (the default on CentOS 8.x and RHEL) would not be detected as being a local filesystem for updating the ledger, resulting in an unnecessary file copy.

To avoid a deadlock in some versions of glibc, a workaround was added, and can be enabled by adding the --emake-try-chain-locks=0 command line option. See the "Known issues" section below for details.

Because the agent to Cluster Manager communication uses TLS by default, the agent image used for AWS EC2, GCP or Azure cloud bursting must also be upgraded to the 11.3 release or later in order for cloud bursting to work.

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

The recommended total amount of RAM for an agent host is 2 GB per agent plus the amount of RAM normally needed to execute your build. For example, if you are running four agents, and your build normally needs 16 GB, you will need ((2 * 4) + 16) = 24 GB.

The upgrade process does not preserve the existing files. Back up the /opt/ecloud/<arch>/cloud directory for Linux or the C:\ECloud\<arch> folder for Windows to a safe location.

Affected kernel versions:

Some versions of glibc — releases roughly in the range 2.26 through 2.30, such as that present in SLES 15 SP2 and SP3 — have a bug in the try read-write lock pthread call that can result in deadlocks. This can cause builds with heavy ledger usage to intermittently hang in the eMake client. As a workaround for this, add the command line option --emake-try-chain-locks=0 to your build, which will avoid the try lock calls, though this will render the tracking of time waiting for locks in the resulting annotation file invalid. Other options would be upgrading your version of glibc, or switching to another distribution.

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