Configure plugin settings
- Navigate to Admin > Plugins in the main menu
- Click on gear icon next to the
GoCD Elastic Agent Plugin for Azureand enter the required plugin configuration.
Note: Configuration marked with (*) are mandatory
Go Server configuration
GoCD Server URL*: This is used by the instance to register with GoCD server. Server hostname must resolve in your container. Don’t use
Agent autoregister timeout (in minutes)*: If an agent running on a virtual machine created by this plugin does not register with this server within the specified timeout period, the plugin will assume that the instance failed to startup and will be terminated.
Agent idle timeout (in minutes): Agent virtual machines will be kept idle for this period before termination, after job completion. This setting can be overridden at the elastic profile.
Resource Group name*: All the agent virtual machines(and its dependencies) will be created in this resource group.
Region name*: The agent virtual machines are created within the specified Azure region. Read more about Azure Regions
Virtual Network Id*: Enter the resource id of the virtual network in which all the agent virtual machines are created. Use Azure client to get the Virtual Network Id of an existing network.
Subnet name(s)*: Enter comma separated subnet names. If multiple subnet names are specified, the plugin chooses a random subnet and creates the agent in it. User can override this from elastic profile.
Network Security Group Id: A network security group contains several default security rules that allow or deny traffic to or from resources. Enter the resource id of the network security group to be assigned to the virtual machine.
A service principal is required by an application to deploy or configure resources through Azure Resource Manager in Azure Stack.
Create the service principal using the following guide
Note down the
Domain/Tenant Id from the response and enter the below fields.
These settings applied based on the platform chosen for the agent virtual machine at Elastic profile level.
For Linux username/sshkey and for Windows username/password fields are captured and applied based on the profile chosen at the Elastic profile level.