Installing eMake on Linux

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.

Using the GUI to install eMake on Linux

Sign in as root.
Double-click the CloudBeesAccelerator-<version>-<platform>-Install installer file to start installation.

Extracting the installation packages to your machine might take several minutes before the installation wizard appears.
When the Welcome screen appears, click Next.
On the Setup Type screen, select Electric Make, and click Next.
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.
Click Next.
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).
  
  For details, see Configuring CloudBees Build Acceleration on Windows - Initializing Visual Studio].
  
  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).
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.
When the Start Copying Files screen appears, review your settings and click Next.
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.

Using the interactive command line to install eMake on Linux

Sign in as root.
Run chmod +x ` on the `CloudBeesAccelerator-<version>-<platform>-Install installer file to ensure it is executable.

Run ./<installer filename> --mode console to start the installation.

The installer displays:

This will install CloudBees Build Acceleration version <version> on your computer.

For information about software configuration and licensing, see the CloudBees Build Acceleration Installation and Configuration Guide.Enter y to continue or n to exit the installer. [n/Y]▼

Continue the installation by entering y.

The installer displays:

Welcome to the CloudBees Build Acceleration installer <version>
  Build: <version>
==========================================================
This installer can install the following packages:

1 - Agent/EFS
          Installs Agent/EFS and Electric Make.
2 - Electric Make
          Installs Electric Make.
3 - Cluster Manager
          Installs Cluster Manager and Electric Make.
4 - Cluster Manager and Agent
          Installs Cluster Manager, Electric Make and Agent/EFS on same host.
Select a package to install by entering the corresponding number:  [2]▼

Enter 2 to select the Electric Make package and then press Enter.

The installer displays:
```
Where do you want to install CloudBees Build Acceleration? [opt/ecloud]▼
```
Accept the default location or type in an alternative location.

If you install eMake in a non-default location, ensure that the same location is used for all agent hosts and the Cluster Manager host.

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.

The installer displays:
```
Install Electric Runner client apps [n/Y]▼
```
Decide if you want to install eRunner client apps. eRunner is a “helper” daemon normally installed on all agent machines.

This daemon listens for commands to execute on agents, facilitating administration tasks. For example, with eRunner you can upgrade all agents at the same time, remotely. Make you selection and press Enter to continue.

If the machine already has eMake installed and you chose to install this version of eMake in a different location, you have the option to allow multiple eMake installations on the same machine. If you don’t allow this, the previous version of eMake will be uninstalled.

If the above conditions are true, the installer displays:
```
Allow multiple EMake installs in separate directories [y/N]▼
```
The installer installs eMake using the configuration details you provided, followed by Installation complete when the install completes.

The installation log file is in the install directory’s root, /opt/ecloud, by default.