If you are installing on a series of identical machines (such as a series of cluster hosts), you can use the “silent” installation method, which installs components automatically without user interaction.
|On Windows, if you invoke the installer from the command line, an “Unknown Publisher” security warning might appear. You can disregard this warning and proceed with installation.|
Use the following command-line options when performing a silent installation. The options are the same values that a user would normally set through the installer interface. Use this format:
This table lists each command-line option’s equivalent in the installer UI and the variable that is set in the installer properties file. You can use the resulting properties file for running silent installations.
|You can use the values “yes”, “y”, “1” and “no”, “n”, “0” interchangeably within installer command-line options.|
|Command-line option||Variable set in the installer properties file||Description|
Equivalent installer UI field
Allow multiple eMake installations in separate directories
Allows multiple eMake installations to exist on the same machine if they are installed in different directories. If you don’t allow multiple eMakes, the previous version of eMake will be uninstalled. This option is available only if you choose a different installation directory from the current eMake installation.
Sets the Cluster Manager Administrator user password.
Indicates if you want to reboot after installing the Agent/EFS. Default: n For Windows, if you use n, the installer does not restart the Agent service; reboot the host to ensure EFS works properly. Windows might prompt before the host is rebooted. For UNIX, the machine does not reboot unless required, even if you specify
Sets the Cluster Manager hostname or IP address for this host to connect to. Example: 126.96.36.199 or winlong-cm
Sets the Cluster Manager server port number for this host to connect to.
y installs eRunnerd on agent machines. Default: y
Indicates if the agents are provisioned on-demand from a cloud such as Amazon EC2 or Kubernetes. Default: n
Sets the number of agents to set up on the host. The maximum is 64.
Sets the password for ECloudInternalUser (Windows only).
Removes old agent log files. If not, the install appends to them. Default: n
y requires an agent-generated key to be entered before commands will run on the agent console port. Default: n
(Linux platforms only) Specifies whether to install EFS. Enable this option if you already installed the
(Linux platforms only) Specifies whether to install LOFS. Enable this option if you already installed the
Default: 0 (n)
Sets the temporary directory for all agent files. On Linux, this directory must not be a symbolic link. Windows default: C:\WINDOWS\temp Linux/UNIX default: /tmp
Sets a list of username/password pairs to be used as login accounts for agents (Windows only).
Backs up the local database only. Remote databases are not backed up. Default: n
Installs eRunner client applications on Cluster Manager and eMake machines. Default: y
Sets the Cluster Manager server port number for unencrypted traffic.
Sets the Cluster Manager server port number for encrypted traffic.
Sets the Cluster Manager database host machine.
Sets the name of the database to create on the database server. If you do not use the default local database, you must provide the name of an existing database.
Sets the user password to use when connecting to the database server.
Sets the database listening port. Use 1433 for MS SQL.
Sets the type of database to use for Cluster Manager.
Sets the user name to use when connecting to the database server.
Sets the Cluster Manager HTTP server port.
Sets the Cluster Manager HTTPS server port.
Rotates Apache logs. Default: y
Migrates the database; this value is meaningful only if performing an upgrade. Default: n
Removes old Cluster Manager log files. If not, the install appends to them. Default: n
Sets the Apache/SSLserver name.
Sets the user to run the Cluster Manager service.
Sets the password to use for the Cluster Manager service user. If not specified, the account that Cluster Manager runs as is used (Windows only).
Runs the installer in debug mode.
Runs the installer with the debug console open.
Sets the port for eRunnerd to listen on.
Removes old eRunnerd logs. If not, the install appends to them. Default: n
Sets the location where the installed directory tree will be located. Use this option when --prefix is a temporary location that is not the final destination for the product.
Ignores the previous configuration.
Sets the mode in which to run the installer. For a console login, standard mode and console mode are identical. For a GUI machine,
Does not install the Microsoft Visual C++ 2005 SP1 Redistributable (Windows only). Default: n
Show the available command-line parameters for installation.
Sets the PDF reader to use.
Sets the installation directory. Windows default: C:\ECloud UNIX default: /opt/ecloud
Sets the property file from which to read installer options.
Removes (1) zip files after installation.
Allows the installer to run when root privileges are not present and disables the execution of installer steps that would require root privileges. This option does not change access privileges. 1 (y) or 0 (n).
Specifies the location for read/write files.
Prevents (1) the installer from starting the agent or Cluster Manager
Sets the temporary directory used by this program.
Runs the installer without installing any files.
Type of installation to perform.
Displays installer version information.
(Windows platforms only) Installs the CloudBees Build Acceleration Visual Studio Integration.
(Windows platforms only) Initializes Visual Studio automatically for these users on your agent hosts. For details, see xInitializing Visual Studio.
An installer properties file is a text file that defines installation parameters. These parameters are the same values that a user would normally set through the installer interface or command line.
To create an installer properties file:
Run an installation with your desired settings.
This creates a properties file (
install.props ) in the top-level install directory.
Use the resulting properties file for subsequent silent installations of the same component type.
Components are installed individually so you must create an installer properties file for each CloudBees Build Acceleration component you intend to install.
The table details the parameters within installer properties files.
Make sure you already have a properties file (
install.props) that was created by a successful installation.
Sign in to the remote machine as root.
Invoke the installer:
# ./<installer filename> --mode silent --propertyfile <properties file>
Make sure you already have a properties file (
install.props) created by a successful installation.
Sign in to the remote machine as Administrator.
Invoke the installer in a DOS shell:
<installer filename> /mode silent /propertyfile <full path\properties file>
If you are performing a silent upgrade on an agent host by running the installation on the host itself, you might be prompted before the machine is rebooted. This prompt occurs if others are logged in to the machine when you run the agent upgrade.
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 Build Acceleration, see Installer Error Messages. The range for Installer error codes is 6000–6999.