Azure VM Agents0.7.0Minimum Jenkins requirement: 1.653ID: azure-vm-agents
A Jenkins Plugin to create Jenkins agents in Azure Virtual Machines (via Azure ARM template).
- Windows Agents on Azure Cloud using SSH and JNLP
- For Windows images to launch via SSH, the image needs to be preconfigured with SSH.
- For preparing custom windows image, refer to Azure documentation
- Linux Agents on Azure Cloud using SSH
- For preparing custom linux image, refer to Azure documentation
How to Install
You can install/update this plugin in Jenkins update center (Manage Jenkins -> Manage Plugins, search Azure VM Agents Plugin).
You can also manually install the plugin if you want to try the latest feature before it's officially released. To manually install the plugin:
Clone the repo and build:
- Open your Jenkins dashboard, go to Manage Jenkins -> Manage Plugins.
- Go to Advanced tab, under Upload Plugin section, click Choose File.
targetfolder of your repo, click Upload.
- Restart your Jenkins instance after install is completed.
To use this plugin to create VM agents, first you need to have an Azure Service Principal in your Jenkins instance.
- Create an Azure Service Principal through Azure CLI or Azure portal.
- Open Jenkins dashboard, go to Credentials, add a new Microsoft Azure Service Principal with the credential information you just created.
Configure the Plugin
Add a New Azure VM Agents Cloud
- Within the Jenkins dashboard, click Manage Jenkins -> Configure System -> Scroll to the bottom of the page and find the section with the dropdown "Add a new cloud" -> click on it and select "Microsoft Azure VM Agents"
- Provide a name for the cloud (plugin will generate one for you if you leave it empty, but it's recommended to give it a meaningful name).
- Select an existing account from the Azure Credentials dropdown or add new "Microsoft Azure Service Principal" credentials in the Credentials Management page by filling out the Subscription ID, Client ID, Client Secret and the OAuth 2.0 Token Endpoint.
- Click on “Verify configuration” to make sure that the profile configuration is done correctly.
- Save and continue with the template configuration (See instructions below).
Add a New Azure VM Agent Template
Click the "Add" in "Add Azure Virtual Machine Template" to add a template. A template is used to define an Azure VM Agent configuration, like its VM size, region, or retention time.
Provide meaningful name and description for your new template.
Provide one or more meaningful labels, e.g. "Windows" or "Linux". Label is used by job to determine which agents will be selected to run the job, so please make sure you give it a meaningful label.
Select the desired region, and VM size from dropdown list.
Select the Storage Account Type, either Standard_LRS or Premium_LRS. Note that some VM size only supports Standard_LRS.
Specify the Azure Storage account name or select an existing Storage account name for storing VM's OS disk. If you choose to create a new one but leave the name blank the plugin will generate a name for you.
Select the disk type between Managed Disk (recommended) or Unmanaged Disk.
Select the retention strategy
- Idle Retention Strategy. You can specify the retention time in minutes. This defines the number of minutes Jenkins can wait before automatically deleting an idle agent. Specify 0 if you do not want idle agents to be deleted automatically.
- Pool Retention Strategy. This retention strategy help you to maintain amount of agents in a specific number. You can specify the retention time in hour and the pool size.
- Once Retention Strategy. This retention strategy make sure to use one agent only once.
Retention time define the time of hour before automatically deleting since the agent created. And the pool size define the agent pool size you want to maintain. If you change your cloud name, template name or most of parameters (e.g. Region, Image), we will delete the existing agents at once and provision the new one according to your new template. But if you only change your Retention Time or Pool Size, we will only scale in, scale out or do nothing for you.
Select a usage option:
- If "Utilize this node as much as possible" is selected, then Jenkins may run any job on the agent as long as it is available.
- If "Only build jobs with label expressions matching this node" is selected, Jenkins will only build a project on this node when that project is restricted to certain nodes using a label expression, and that expression matches this node's name and/or labels. This allows an agent to be reserved for certain kinds of jobs.
Select a built-in image, you can choose between Windows Server 2016 and Ubuntu 16.04 LTS. You can also choose to install some tools on the agent, including Git, Maven and Docker (JDK is always installed).
Specify Admin Credentials (a username/password credentials), this is the username and password if you want to log into the agent VM.
Click Verify Template to make sure all your configurations are correct, then Save.
Run Jenkins Jobs on Azure VM Agents
After you configured an Azure VM agent template, when you run a new Jenkins job, Jenkins will automatically provision a new Azure VM only if there is no executor available.
A more common scenario is you want to restrict some jobs to always be running on a particular VM agent instead of Jenkins master. To achieve that:
- Open your Jenkins project, under General, check "Restrict where this project can be run".
- In Label Expression, fill in the label you assigned to your VM template.
- Save and run the job, you'll see your job is running on the VM agent even if Jenkins master is free.
For how to select agent in pipeline, refer to this doc.
Use a Custom VM Image
The built-in image only has a clean Windows or Ubuntu OS and some tools like Git and Maven installed, in some cases, you may want to have more customization on the image. To use a custom image:
In Image Configuration, select "Use Advanced Image Configurations".
Choose between two possible alternatives:
- Use a custom user image (provide image URL and OS type - note, your custom image has to be available into the same storage account in which you are going to create agent nodes);
- Using any marketplace image by specifying an image reference (provide image reference by publisher, offer, sku and version). You can get the publisher, offer and sku by looking at the ARM template of that image.
For the launch method, select SSH or JNLP.
- Linux agents can be launched only using SSH.
- Windows agents can be launched using SSH or JNLP. For Windows agents, if the launch method is SSH then check Pre-Install SSH in Windows Slave or image needs to be custom-prepared with an SSH server pre-installed.
We recommend to use SSH rather than JNLP, for you need less init codes and get much clearer logs.
When using the JNLP launch option, ensure the following:
- Jenkins URL (Manage Jenkins -> Configure System -> Jenkins Location)
- The URL needs to be reachable by the Azure agent, so make sure to configure any relevant firewall rules accordingly.
- TCP port for JNLP agent agents (Manage Jenkins -> Configure Global Security -> Enable security -> TCP port for JNLP agents).
- The TCP port needs to be reachable from the Azure agent launched using JNLP. It is recommended to use a fixed port so that any necessary firewall exceptions can be made.
If the Jenkins master is running on Azure, then open an endpoint for "TCP port for JNLP agent agents" and, in case of Windows, add the necessary firewall rules inside virtual machine (Run -> firewall.cpl).
For the Initialization Script, you can provide a script that will be executed after the VM is provisioned. This allows to install any app/tool you need on the agent. Please be noted you need to at least install JRE if the image does not have Java pre-installed. We prepared a sample script for Linux via SSH, Windows via SSH and Windows via JNLP. Please find details in help button.
If you hit the storage scalability limits for your custom images on the storage account where the VHD resides, you should consider using the agent's temporary storage or copy your custom image in multiple storage accounts and use multiple VM templates with the same label within the same agent cloud.
For more details about how to prepare custom images, refer to the below links:
Init script should finish in 20 minutes (this time can be configured in Deployment Timeout setting of Azure Profile Configuration). It's not recommended to run complex init script, if the init script is expected to take a long time to complete, it is recommended to use a custom-prepared image.
If you choose Use Advanced Image Configurations, you can click on Advanced button where you can find more VM configurations:
Virtual Network Name, Virtual Network Resource Group Name and Subnet name: by default the VM does not belong to any virtual network, you can provide one if you want the VM to be in a virtual network for network security. Please be noted the virtual network must exist.
Make VM agent IP private: by default the plugin will create a public IP for the VM so it's public accessible on internet. Check this option if you don't want the public IP to be created.
Make VM agent IP private can make the VM more secure, but if you configured to use SSH to launch agent, Jenkins master needs to be able to access the VM. So in this case you need to also specify virtual network and subnet name so the agent and Jenkins master are in the same subnet.
Network Security Group Name: add the VM to a network security group.
JVM Options: specify JVM options.
Number of Executors: specify the number concurrent builds that a VM agent can run at the same time.
Disable template: disable this template temporarily.
Configure VM Template using Groovy Script
In some cases you may want to configure the VM template using script so it can be automated instead of manually configure it in UI. Jenkins supports groovy script that can automates such operation. Here is a sample groovy script that creates a new Azure cloud and VM template. You can run it in Manage Jenkins -> Script Console.
This sample only contains a few arguments of builder, please find all the arguments in folder builders.
Version 0.7.0, 2018-04-09
- Support custom managed disk JENKINS-48076
- Add more checks in Template Name, Admin/Password JENKINS-49150
- Add sync logic to prevent issues when using only shutdown JENKINS-49021
- Clean unused warning logs JENKINS-48901
- Add Cloud Statistics cleaner JENKINS-48345
- Add blank choice for storage account to reduce UI issues related to existing storage account JENKINS-48253
- Check whether reuse existing storage account JENKINS-47923
- Show detail error message when the template cannot be deployed. JENKINS-46337
- Resolve vm delete issue if related cloud have been deleted. JENKINS-49473
Version 0.6.2, 2018-02-24
- Use Tls1.2 to fix the bug in SSH initialization
- Support Windows Server 1709 as SSH slave
Version 0.6.1, 2018-02-09
- Fix location verification on non-global clouds
Version 0.6.0, 2018-01-02
- Use deallocation instead of powerOff when configured shutdown only
- Add built-in windows image with docker
- Redesign verification task to improve performance
- Fix launching issues when using performance limited vms
Version 0.5.0, 2017-11-29
- Add support for the Managed Service Identity (MSI) as credential
- Clean init scripts after the deployment
- Fix some minor bugs
Version 0.4.8, 2017-11-07
- Add Cloud and Template builder with fluent interface
- Add pool retention strategy and once retention strategy
- Fix bugs and improve performance
- Maven version in built-in image update to 3.5.2
- Add Third Party Notice
Version 0.4.7.1, 2017-08-10
- Fixed an issue that built-in init script cannot run correctly under Linux.
Version 0.4.7, 2017-08-01
- Built-in image support. Now besides manually fill in image reference and init script, you can select from two built-in images, Windows Server 2016 and Ubuntu 16.04 LTS.
- Auto tool installation on VM agents. If you're using built-in image, you can choose to install Git, Maven or Docker.
- SSH support for Windows agent. You can now use SSH to launch Windows agent.
- Support managed disk for VM agent.
- Allow user to specify the name for the cloud. This fixes the issue that one cloud will be ignored if you have two with same subscription ID and resource group name.
- Various minor bug fixes.
Version 0.4.6, 2017-06-20
- Add LogRecorder for Azure VM Agent plugin to make it easier for troubleshooting
- Fix an issue that Jenkins crashes in some cases when CloudStatistics is enabled
- Improve VM template creation, you're now able to select from existing resource groups and storage accounts.
Version 0.4.5.1 Beta, 2017-06-09
- Fixed a backward compatibility issue that storage type becomes empty when reading a configuration created from an older version. (JENKINS-44750)
Version 0.4.5 Beta, 2017-06-02
- Added the option to specify different resource group for virtual network. (JENKINS-43909)
- Support multiple cloud profiles with the same subscription ID (JENKINS-43704)
- Support premium storage account for VM template (JENKINS-43097)
- Support Cloud Statistics Plugin (JENKINS-42799)
Version 0.4.4 Beta, 2017-04-12
- Added the option to deploy VM Agents without a public IP. (JENKINS-40620)
- Added the ability to attach a public IP for an already deployed agent. The user need to go to the Nodes management page and configure the desired Azure VM Agent.
- Added the option to attach an existing Azure Network Security Group to the provisioned agents
- Fixed the 'Usage' parameter. (JENKINS-42037)
- Fixed a Null Pointer Exception while trying to fill the VM Size dropdown. (JENKINS-42853)
- The agent password verification now allows more special characters. (JENKINS-43243)
Version 0.4.3 Beta, 2017-03-03
- The plugin now depends on the Azure Credentials plugin
- Existing credentials are now working when upgrading the plugin (JENKINS-42479)
- Fixed an issue where deployments in some existing Azure Resource Groups might have failed
- The plugin now removes the leftover empty containers after a custom-image agent was deleted.
Version 0.4.2 Beta, 2017-01-16
- Extend support to all Azure regions and available VM sizes (JENKINS-40488)
- Fixed an edge case where provisioned VMs were not removed after they were used (JENKINS-41330)
- The fix will ensure that newly created resources are properly disposed, but it won't disposed of any resources deployed with the plugin before and including version 0.4.1
- Updated the 'Max Jenkins Agents Limit' label in the cloud configuration page to reflect the quota on the number of agents the plugin is allowed to deploy in a resource group (JENKINS-41568)
- Other minor fixes and improvements
Version 0.4.1 Beta, 2016-12-13
- Verify that the storage account name is valid during template verification (JENKINS-40289)
- The auto-generated storage account name is unique across Azure (JENKINS-40288)
- The SSH session is re-established after the init script runs (JENKINS-40291)
- Other minor fixes and improvements
Version 0.4.0 Beta, 2016-12-06
- Initial release