Before You Install CloudBees Accelerator

You can install the software using a GUI, a "silent" installer, or (on Linux and Solaris ) an interactive command-line interface.Not all instructions are the same for each platform. Follow the instructions carefully for your platform. Read the procedures thoroughly before attempting to install, configure, or uninstall any component.

Supported Deployment Models for CloudBees Accelerator 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

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

  • On Windows, the Huddle installer file is the same file for 32-bit or 64-bit. On Linux, you must use either the 32-bit or the 64-bit installer file.

  • 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. On 64-bit machines, 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. On 64-bit machines, 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. On 64-bit machines, 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. On 64-bit machines, 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. On 32-bit machines, 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. On 32-bit machines, 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. On 32-bit machines, 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. On 32-bit machines, the installer creates a link from this directory to C:\ECloud\i686_win32\lib.

  • The installer file installs both 32-bit and 64-bit versions of eMake. But on Windows, the installer adds <InstallDir>\i686_win32\bin to the PATH environmental variable to point to 32-bit eMake. If you are running 64-bit Windows, you can modify the PATH environment variable to use 64-bit eMake if needed.

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

  • On Windows, the installer automatically determines whether to install the 32-bit or 64-bit agents and Huddle Server based on the machine architecture. No user action is required. On Linux, the 32-bit installer will install the 32-bit agents and Huddle Server, and the 64-bit installer will install the 64-bit agents and Huddle Server.

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

  • On Linux, after installation, you must add either the 32-bit bin location or the 64-bit bin location to your PATH environment variable. You can do this by sourcing the /opt/ecloud/i686_Linux/conf/ecloud.bash.profile file or the /opt/ecloud/i686_Linux/conf/ecloud.csh.profile file as appropriate for your shell.

Downloading the Accelerator Software

You can download an Accelerator installer file using any of the following methods.

cloudbees.com Website

Go to https://www.cloudbees.com/products/accelerator/trial, then fill in the form with your contact information, and then click Submit.

CloudBees ShareFile Website

Sign in to https://cloudbees.sharefile.com/Authentication/Login, 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/Authentication/Login, then browse to Folders > Shared Folders > products > Accelerator > release_11.1 > 11.1.0.88023 > linux, and then click the ElectricAccelerator-11.1.0.88023-Linux-x86_64-Install file to download it.

Express Mode Installation Defaults

Table 1. 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

Table 2. 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

Table 3. 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 and Installer Error Messages

The installation log file ( install_$timestamp.log ) is in the installation directory’s root by default. For example, /opt/ecloud/install_20190701_1502.log on Linux or C:\ECloud\install_20190701_1502.log on Windows.

Installer error messages appear in this file. For detailed information about the most common error messages for the Installer component of CloudBees Accelerator, see Installer Error Messages. The range for installer error codes is 6000–6999.