Installing eMake on Windows

eMake can be installed on a networked machine or on a shared file server accessible to other build machines. Wherever eMake is installed, it must have access to the Cluster Manager machine and agents on the cluster host machines. If you are upgrading a previously installed CloudBees Build Acceleration version, follow the upgrade instructions before attempting to install the new version.

An eMake-only installer is available, which lets you streamline eMake client installation.

After eMake is installed, you must configure eMake for your build environment and enable communication with the Cluster Manager. For details, see Setting Up CloudBees Build Acceleration.

You can install the Cluster Manager and agents at the same time on the same machine.

  1. Sign in as Administrator. (You must be a member of the Administrator group—Administrator privileges are not sufficient.) If you are running rdp on the Cluster Manager server, ensure that rdp is in installation mode: change user/install.

  2. Double-click the CloudBeesAccelerator-<version>-<platform>-Install installer file.

    (For Windows Server 2012 or later, the administrator user must right-click the file and select Run as administrator.)

    If you have not already downloaded the CloudBees Build Acceleration installer, see Downloading the CloudBees Build Acceleration Software. The installation packages might need a few minutes to extract. If a security alert pop-up appears, click unblock and continue. ** CloudBees Build Acceleration requires the Microsoft Visual C++ 2005 SP1 Redistributable. If it is already installed, select the checkbox.

  3. Click Next to continue.

  4. When the Welcome screen appears, click Next.

  5. On the Setup Type screen, select Electric Make, and click Next.

  6. On the Choose Destination Location screen, accept the default installation directory or browse to select an alternative directory.

    Ensure the eMake path matches the path used for the installed Electric Agent.

    Do not choose an alternative directory that includes spaces in the name. Spaces can create problems when configuring connections with other command-line-based components.

    An error appears if you do not have permission to write to the alternative directory. If this occurs, you must either acquire permission or exit the installer, then lsign in as root, and then restart the installation.

  7. Click Next.

  8. On the Base Setup screen, modify the following settings as needed, and then click Next :

    • (Optional) Unselect Install Electric Runner client applications to decline installation of the tools to manage and administer an CloudBees Build Acceleration host cluster (this is selected by default).

      For a description of these tools, see Using Cluster Manager Administration Tools.

    • (Optional) Unselect Install Visual Studio Plugin to decline installation of the CloudBees Build Acceleration Visual Studio Integration (this is selected by default).

    • (Optional) Select Initialize Visual Studio for ECloudInternalUsers to initialize Visual Studio automatically for these users on your agent hosts (this is unselected by default).

      Using this checkbox can add up to 30 minutes to the installation time (depending on the number of agents and the number of installed Visual Studio versions).
  9. If the machine already has eMake installed and you chose to install this version of eMake in a different location, you can allow multiple eMake installations on the same machine. If you don’t allow this, the previous version of eMake will be uninstalled. Choose your option and click Next.

  10. When the Start Copying Files screen appears, review your settings and click Next.

  11. The Installing screen displays while the installation proceeds. When installation is finished, the Complete screen displays. Click Finish.

Installation is complete. The installation log file is in the install directory’s root, by default.