Before You Install ElectricAccelerator

You can install the software using a GUI, a "silent" installer, or (on Linux and Solaris) an interactive command-line interface.

For information about platform support such as operating systems, cloud-based and Kubernetes support, Make versions, eMake emulation, databases, bitnesses, and Visual Studio versions, see CloudBees Accelerator Supported Platforms.

Supported Deployment Models for ElectricAccelerator Components

Not all combinations of the Cluster Manager, agents, and eMake components can be installed on the hosts in your cluster. Following are the supported combinations:

  • Cluster Manager, agents, and eMake on a single host

  • Cluster Manager and eMake on one host, and agents on other hosts

  • Cluster Manager on one host, and eMake and agents on other hosts

Installing the Cluster Manager and agents on one host with eMake on a separate host is not supported.

Cluster Manager and Agent Installation Location Limitations

Electric Cloud does not support installation of the Cluster Manager or agents on the following:

  • NFS

  • CIFS

  • Samba shares

32-Bit Versus 64-Bit Versions

  • On Windows and Linux, the installer file always installs both the 32-bit and 64-bit versions of eMake. On Solaris, it installs only the 32-bit version.

  • 64-bit executables are installed in a subdirectory of <InstallDir>/<arch>64/bin.

    • For example, on Linux, if you install in /opt/ecloud, the executables are installed in /opt/ecloud/i686_Linux/64/bin. The installer creates a link from this directory to /opt/ecloud/i686_Linux/bin.

    • For example, on Windows, if you install in C:\ECloud, the executables are installed in C:\ECloud\i686_win32\64\bin. The installer creates a link from this directory to C:\ECloud\i686_win32\bin.

  • 64-bit libraries are installed in a subdirectory of <InstallDir>/<arch>64/lib.

    • For example, on Linux, if you install in /opt/ecloud, the executables are installed in /opt/ecloud/i686_Linux/64/lib. The installer creates a link from this directory to /opt/ecloud/i686_Linux/lib.

    • For example, on Windows, if you install in C:\ECloud, the executables are installed in C:\ECloud\i686_win32\64\lib. The installer creates a link from this directory to C:\ECloud\i686_win32\lib.

  • 32-bit executables are installed in a subdirectory of <InstallDir>/<arch>32/bin.

    • For example, on Linux, if you install in /opt/ecloud, the 32-bit executables are installed in /opt/ecloud/i686_Linux/32/bin. The installer creates a link from this directory to /opt/ecloud/i686_Linux/bin.

    • For example, on Windows, if you install in C:\ECloud, the executables are installed in C:\ECloud\i686_win32\32\bin. The installer creates a link from this directory to C:\ECloud\i686_win32\bin.

  • 32-bit libraries are installed in a subdirectory of <InstallDir>/<arch>32/lib.

    • For example, on Linux, if you install in /opt/ecloud, the 32-bit executables are installed in /opt/ecloud/i686_Linux/32/lib. The installer creates a link from this directory to /opt/ecloud/i686_Linux/lib.

    • For example, on Windows, if you install in C:\ECloud, the executables are installed in C:\ECloud\i686_win32\32\lib. The installer creates a link from this directory to C:\ECloud\i686_win32\lib.

  • The agent installer automatically determines whether to install the 32-bit or 64-bit agents based on the machine architecture. No user action is required.

  • The Accelerator installer automatically sets the path to the appropriate bitness (32-bit or 64-bit) for your platform. To use 32-bit on a 64-bit machine (such as when you need to do 32-bit builds), you must edit the environment variable path to include the 32-bit bin location before the /opt/ecloud/i686_Linux/bin location.

Downloading the Accelerator Software

Sign in to https://cloudbees.sharefile.com, then browse to Folders > Shared Folders > products > Accelerator > release_ version > build_number > platform, and then click the appropriate installer file to download it.

For example, sign in to https://cloudbees.sharefile.com, then browse to Folders > Shared Folders > products > Accelerator > release_11_0 > 11.0.0.84351 > linux, and then click the ElectricAccelerator-11.0.0.84351-Linux-x86_64-Install file to download it.

Express Mode Installation Defaults

You can perform an Express-mode installation for the three main Accelerator components: the Cluster Manager, agents, and eMake. The following tables list the default values for this mode.

Cluster Manager

Parameter Default value

Cluster Manager host IP address

localhost

Install Electric Runner service

Y

Apache port (Cluster Manager HTTP port)

80

Apache SSL port (Cluster Manager HTTPS port)

443

Cluster Manager server port

8080

Cluster Manager secure server port

8081

Service user

(Windows) ""

(Linux) eacmuser

Database type

MariaDB

Cluster Manager admin name

admin

Cluster Manager admin password

changeme

Database port

3306

Database host

localhost

Database name

ecloud

Database user

root

Database password

ecloud

Install directory

(Windows) C:/ECloud

(Linux) /opt/ecloud

(Linux) Cluster Manager group name

nobody

Agent

Parameter Default value

Cluster Manager host IP address

localhost

Install Electric Runner service

Y

Cluster Manager Accelerator server port

8030

Electric Runner server port

2411

Install directory

(Windows) C:/ECloud

(Linux) /opt/ecloud

Cluster Manager name

localhost (but can be changed in Express mode)

Cluster Manager port

8030

Agent secure console port

N

Agent is on-demand host

N

Remove logs

N

Reboot if needed

N

Agent temporary directory

(Windows) C:/Windows/temp

(Linux) /tmp

Install Electric Runner server

Y

Electric Runner port

2411

Remove logs

N

eMake

Parameter Default value

Install directory

(Windows) C:/ECloud

(Linux) /opt/ecloud

Install Electric Runner client apps

Y

Allow multiple eMake installations in separate directories

N

Installation Log File

The installation log file is in the installation directory’s root by default.