Install an express agent (full installer)

This page covers how to install CloudBees CD/RO agents using the CLI-based Express Agent option of Linux full installers.

The Express Agent option installs the following CloudBees CD/RO components on the host machine:

Agent
CloudBees CD/RO tools (Required)

Before you start

The following are important knowledge prerequisites to review before starting this procedure:

CloudBees recommends reviewing the following resources before installation:

The Express Agent option is meant for installing an agent that will be used as a remote agent for a server running on a separate machine.

For production environments, CloudBees recommends installing each CloudBees CD/RO component on separate machines using the Advanced installation option.

Additionally, there are specific agent security recommendations available at Agent security recommendations.

Perform an Express Agent installation

If you have not already done so, download the full installer file. To download this version, select:
- Linux full installer: 2024.12.0.177508
For more details on installers, refer to Install CloudBees CD/RO on traditional platforms.

For legacy installer downloads, navigate to CloudBees CD/RO downloads.
Start the installer:
1. Enter the following command to make the installer file executable:
  Command
  Current version
  chmod +x CloudBeesFlow-x64-<version>
  ▼
  chmod +x CloudBeesFlow-x64-2024.12.0.177508
  ▼
2. Start the installation:
  
  For more information about required user privileges, refer to Linux services user permissions.
  - For root or sudo installations, run:
    
    Root or sudo procedures
    
    Command
    Current version
    
    ./CloudBeesFlow-x64-<version>
    ▼
    
    ./CloudBeesFlow-x64-2024.12.0.177508
    ▼
    
    For root or sudo installations on Linux systems with a graphical interface systems, run:
    
    Command
    Current version
    
    ./CloudBeesFlow-x64-<version> --mode console
    ▼
    
    ./CloudBeesFlow-x64-2024.12.0.177508 --mode console
    ▼
  - For non-root/non-sudo installations, run:
    
    Non-root/non-sudo procedure
    
    Command
    Current version
    
    ./CloudBeesFlow-x64-<version> --nonRoot
    ▼
    
    ./CloudBeesFlow-x64-2024.12.0.177508 --nonRoot
    ▼
    
    For non-root/non-sudo installations on Linux systems with a graphical interface systems, run:
    
    Command
    Current version
    
    ./CloudBeesFlow-x64-<version> \ --nonRoot \ --mode console
    ▼
    
    ./CloudBeesFlow-x64-2024.12.0.177508 \ --nonRoot \ --mode console
    ▼
    
    A warning about automatic server start-up with non-root/non- sudo installations appears. Enter Yes to dismiss the warning.
The installer launch prompt appears. Enter Y to continue.
A prompt appears that describes the available installation types.
1. Enter expressAgent.
The following prompt appears:
```
Discover the plugins directory from a remote CloudBees CD/RO server? [n/Y]▼
```
1. Enter Y for the agent to be able to use shared plugins on a remote CloudBees CD/RO server.
  
  You should allow access to the plugins directory so agents have access to collections of features, third-party integrations, and third-party tools.
The following prompt appears:
```
Create a resource for the agent being installed on a remote CloudBees CD/RO server? [n/Y]▼
```
1. Enter Y to create a resource for this agent on your remote CloudBees CD/RO server.
The following prompt appears:
```
Register the agent as a trusted agent? [y/N]▼
```
Making an agent trusted restricts the agent to one CloudBees CD/RO server. The agent will not respond to incoming communication from any other CloudBees CD/RO server. This is useful when you want to create a secure production environment, but generally not needed for test or development systems.

You can run gateways without trusted agents. However, you should use gateways with trusted agents to prevent security issues in the firewall between zones connected by a gateway.

There are exceptions to using gateways without trusted agents:
- The firewall between two zones is not required in your environment or is needed only to protect the CloudBees CD/RO server.
- There is a specific reason to use gateways without trusted agents, such as a requirement to prevent unauthorized users from accessing your network. All incoming traffic from the internet is routed to a data center through a load balancer, and the load balancer routes the traffic to the appropriate machine in your network.
  1. Choose one of the following options:
    
    If a gateway is used to communicate with the CloudBees CD/RO server, you must select y. This option allows you to create a trusted network connection between the agent and server under the same certificate authority. This will allow the agent and the CloudBees CD/RO server to communicate across the network.
    
    If there is no gateway between the agent and CloudBees CD/RO server, enter n.
The following prompt appears:
```
Create repository and/or agent in the default zone? [n/Y]▼
```
1. Enter Y to create the agent in the default zone.

The following prompt appears:

Specify the host:port of your remote CloudBees CD/RO server other components being installed can connect to. Including the port is only required if
not using the default port (8443). []▼

Enter the URL of the host CloudBees CD/RO server.

The following prompt appears:
```
Specify the CloudBees CD/RO username for logging into "<CDRO-server>". [admin]▼
```
1. Press Enter to use the admin CloudBees CD/RO account to connect the agent, or specify another user to use to log into CloudBees CD/RO.
  
  This user must have sufficient permissions to register the agent.
The following prompt appears:
```
Specify the password for "<username>" on "<CDRO-server>". []▼
```
1. Enter the password of the CloudBees CD/RO user you are using to log into CloudBees CD/RO
If you selected to create a resource on the remote CloudBees CD/RO server, the following prompt appears:
```
Specify the name of the resource to create on "<CDRO-server>". []▼
```
1. Enter name of the resource to create on the CloudBees CD/RO server.

The following prompt appears:

Specify the hostname of the installed agent to create a new resource. []▼

Enter the hostname of the installed agent.

The following prompt appears:

Specify the name of the default workspace for the new resource "<agent-resource-name>". [] default▼

Enter a default workspace name.

The following prompt appears:

Specify the URL for the agent gateway in the format 'https://ipOrHostname:port' []▼

Enter the URL to use as the agent gateway.

If you did not select to use the default zone, the following prompt appears:
```
Specify the zone name for the agent and/or repository. []▼
```
1. Enter a zone name for the agent.

The following prompt appears:

Specify the system user the agent will run as []▼

Provide the system user to use when running agent services.

If you specify root as the agent service user, the following prompt appears:

For security reasons, CloudBees strongly recommends NOT using the 'root' user to run agent processes in production environments. For more
information, refer to:

https://docs.cloudbees.com/docs/cloudbees-cd/latest/install-trad/agent-config-recommendations

Do you still want to continue using the 'root' user to run agent processes? [y/N]▼

CloudBees strongly recommends not running the agent services as a root user. This can pose significant security concerns if the agent becomes compromised.

To accept these security risks and run the agent as root, enter Y.

The following prompt appears:
```
Specify the system group the agent will run as []▼
```
1. Provide the system group of the user being used to run the agent services.

The CloudBees CD/RO agent installation starts. A success prompt is shown when the installation is complete.

Configure autostart for non-root environments

For installations performed as a Windows Administrator or with Linux root or sudo privileges, CloudBees CD/RO components start automatically upon completing the installation and during system boot. However, for non-root/non-sudo Linux installations CloudBees CD/RO components do not have the permissions to start automatically.

To configure autostart for non-root or non-sudo Linux installations of CloudBees CD/RO components, refer to Configure autostart for non-root/non-sudo Linux installations.