Running an Express Server Command-Line Installation

3 minute read

This option installs the CloudBees CD server, built-in database, web server, and repository server on one machine. The default CloudBees CD server settings are used. A local agent (required for running jobs), and CloudBees CD tools are also installed.

This option is available via a “full” installer file (see CloudBees CD Installer Files ). This option is best for quickly installing the CloudBees CD software for evaluation purposes.

Review Before You Install CloudBees CD before performing this procedure.

NOTE:

+ The built-in database is not supported in a clustered CloudBees CD configuration.

  1. Enter the following command to make the installer file executable:

    chmod +x ./CloudBeesFlow-<version>
  2. Do one of the following to start the installation:

    • For installations with root or sudo privileges, enter:

      ./CloudBeesFlow-x64-<version>

    • For installations with root or sudo privileges and the X Window System, override the installer GUI by entering:

      ./CloudBeesFlow-x64-<version> --mode console

    • For non-root/non-sudo installations, enter:

      ./CloudBeesFlow-x64-<version> --mode console --nonRoot

      After this command, enter Y at the following message:

      Do you want to proceed installation as non-root user? [n/Y]

      The following prompt appears:

      Copyright (c) 2006-2018, CloudBees, Inc. All rights reserved.
      This will install CloudBees CD on your computer. Continue? [n/Y]
  3. Continue the installation by entering y.

    The following prompt appears:

    Specify the type of setup you would like to perform: expressServer, expressAgent, or advanced. [expressServer]
  4. Enter: expressServer.

    The following prompt appears:

    Specify the install directory (for program files and binaries). [/opt/electriccloud/electriccommander]
  5. Press Enter to accept the default installation directory or enter a new directory.

    The following prompt appears:

    Specify the user the server, web, and/or repository will run as. []
  6. Enter a user name.

    This is the user who owns the CloudBees CD server, repository server, and web server processes. For example, you might enter build.

    The following prompt appears:

    Specify the group the server, web, and/or repository will run as. []
  7. Enter a group name.

    This is the group who owns the CloudBees CD server, repository server, and web server processes. For example, you might enter build.

    The following prompt appears:

    Use the same service account for the agent (not recommended for production systems)? [y/N]

    For security reasons in production environments, you should use a separate user and group for the agent service. This is because the server service has permission to read the key file: /opt/electriccloud/commander/conf/passkey in Linux or C:\ProgramData\Electric Cloud\ElectricCommander\conf\passkey in Windows. The key file is used to decrypt passwords stored in CloudBees CD. Using a different user and group for the agent service ensures that a process running on the agent cannot access the key file.

  8. Choose one of the following options:

    • Enter y to use the same user and group for the agent service. This is not recommended for production systems.

    • Enter n to use a separate user and group for the agent service.

      The following prompt appears:

      Specify the user the agent will run as. []
  9. Enter a user name.

    This is the user who owns the CloudBees CD agent process. For example, you might enter build.

    The user/group that the agent runs as must have permission to write to the $INSTALL_DIRECTORY/log directory. If you specify root, enter y when the following confirmation appears:

    It is not recommended to use the 'root' user for running the agent process. Please confirm if you would like to proceed [y/N]

    The following prompt appears:

    Specify the group the agent will run as. []
  10. Enter a group name.

    This is the group that owns the CloudBees CD agent process. For example, you might enter build.

  11. For non-root/non- sudo Linux installations, configure autostart for the CloudBees CD services.

CloudBees CD is installed on the machine. When the installation completes successfully, a message that contains the line CloudBees CD <version> was successfully installed! appears.