Configuring CloudBees Flow Agents

1 minute read

You must configure CloudBees Flow agents to function within a resource pool.

Transport Layer Security (TLS) has replaced Secure Sockets Layer version 3.0 (SSLv3) on the CloudBees Flow server and the CloudBees Flow web server.
  1. Start and log in to CloudBees Flow.

  2. Go to the Cloud > Resources page.

  3. Delete any resource named local .

  4. Create a resource pool named local .

  5. Create resources for all the machines that had the CloudBees Flow agent software installed.

  6. Add agent resources to the local resource pool.

    Choose the appropriate step for your approach.

    • If you are creating a reliability configuration where each CloudBees Flow server machine also has an agent installed, the local resource pool should consist of the set of agents local to the CloudBees Flow server machines.

    • If you are creating a performance configuration where none of the CloudBees Flow server machines have agents installed, the local resource pool (which in this configuration is not actually local to the servers) should contain several agents to handle any work that may be assigned. For example, work may be assigned because of old default resource settings.

  7. Verify that the default resource pool contains two or more resources for reliability.

    You must create and add resources to this pool if none exist.

    1. Go to the Administration > Server page.

    2. Click on the Settings link near the top right to open the Edit Server Settings form.

    3. Set the Server IP address entry in the form to the fully qualified domain name of your CloudBees Flow server’s load balancer.

      This setting controls how agents contact the CloudBees Flow server when they send results from jobs and similar prompts.