Installing the Backward-Compatibility Package on Agent Machines

CloudBees recommends that all components (Cluster Manager, Agent/EFS, and eMake) on all machines in the cluster are upgraded to the latest version. However, you can still use eMake 8.0 with Agents on Agent/EFS machines running versions as old as 7.2, as long as a specific version of backward compatibility package (BCP) is installed on those Agent/EFS machines that corresponds to each version of eMake host that those agents must service.

CloudBees provides archives of eMake versions on the CloudBees ShareFile site.

There might be different reasons why you want to install the backward-compatibility package:

  • You have new agents in the cluster that have only the most recent version of CloudBees Build Acceleration, and you have old agents that were upgraded to the most recent version. To allow old eMakes to use the new agent machines, you must install the backward-compatibility package on the new agents.

  • You encountered incompatibility error messages, indicating the eMake and agent software versions are not compatible:

ERROR EC1050: 049300C4:The protocol version of Electric Make (45) is incompatible with the software installed on the CloudBees cluster 192.168.6.8 (55).You need to upgrade your copy of Electric Make; aborting build

ERROR EC1050: 049300C4:The protocol version of this application (45) is incompatible with the software installed on the Electric CloudBees Build Acceleration cluster 192.168.6.8 (55).You need to upgrade your client application; aborting build

Installing on a Single Agent Machine

  1. Open a terminal window.

  2. Change to the CloudBees installation directory (for example C:\ECloud ` or `/opt/ecloud ).

  3. Download the appropriate set of archive files (for example, i686_win32_bcp.zip [all previous eMake versions] or i686_win32_7.0.0_bcp.zip [a single eMake version]) from the CloudBees ShareFile site: accelerator/emake_archive/< platform >.

  4. Unpack the archive in the current directory (< installDir >). For Windows, make sure the extraction destination is < installDir > without any sub-directories, such as ` C:\ECloud`.

  5. Repeat the process for each new agent machine.

Installing on Multiple Agent Machines

  1. Open a terminal window.

  2. Change to a temporary directory (such as ` /var/tmp`, or ` C:\Windows\Temp` ).

  3. Download the appropriate set of archive files (for example, i686_win32_bcp.zip [all previous eMake versions] or i686_win32_7.0.0_bcp.zip [a single eMake version]) from the CloudBees ShareFile site: accelerator/emake_archive/< platform >.

  4. Unpack the archive in the current directory. For Windows, make sure the extraction destination is the temporary directory (or the directory from step 2) without any sub-directories, such as ` C:\Windows\Temp`.

  5. Run (as an example): clusterupload --cm=<cmname> i686_win32 C:\ECloud.

Protocol Changes

Occasionally, CloudBees Build Acceleration might contain protocol changes that make it necessary to update the eMake version on the build machines. An eMake-only installer is available for this type of update.