Elastic Agents
    Your query search resulted in no results.

    GoCD Elastic Agents


    Elastic Agents is an extension-point in GoCD that allows for on-demand agents which are created and provisioned by an elastic-agent plugin when there are jobs to be executed, and terminated when the agents are running idle. These agents can be in a data center or in the cloud or both, and may be physical or virtual.

    Developers can start building their own elastic-agent plugins by forking the skeleton plugin and looking at a sample docker plugin, docker swarm plugin as an example reference implementation.

    Why elastic agents?

    A feature like this can allow for more efficient use of agent machines, can allow flexible scaling and in many cases, can reduce the cost of running agents. Imagine an automated performance test which runs occasionally and needs a lot of machines. These machines can be started at the beginning of the performance test, possibly using some cloud service, and then brought down when not needed. This feature should enable a more flexible and dynamic build grid.

    Configuration of elastic agents

    Using GoCD elastic agents requires downloading and installing one of the available elastic agents plugin.

    Once the plugin is downloaded and installed, make sure to:

    1. Setup and configure the plugin from the plugin settings page (Admin > Plugins).
    2. Configure an elastic agent profile (Admin > Elastic Agent Profiles).
    3. Associate the elastic agent profile with one or more jobs.


    There are a few basic concepts to understanding the elastic agent plugins in GoCD:

    Plugin Settings

    Plugin settings will usually contain the connection settings so that the GoCD server can connect to the elastic provider. An elastic provider depending on the plugin may be a docker server, or a kubernetes cluster.

    Elastic Agent Profile

    An elastic agent profile will usually contain the configuration for your agent. Depending on the plugin used, this may contain the machine image (ami, docker image), size of the CPU/memory/disk, network settings among other things.

    Once an elastic agent profile is defined, it should then be associated with a particular job. It’s possible to define several profiles for different types jobs.