You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-10Lines changed: 9 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ A Jenkins Plugin to create Jenkins agents in Azure Virtual Machines (via Azure A
7
7
8
8
Supported features:
9
9
10
-
1. Windows Agents on Azure Cloud using SSH and JNLP
10
+
1. Windows Agents on Azure Cloud using SSH and Inbound agent connection
11
11
* For Windows images to launch via SSH, the image needs to be preconfigured with SSH.
12
12
* For preparing custom windows image, refer to [Azure documentation](http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-capture-image-windows-server/)
13
13
2. Linux Agents on Azure Cloud using SSH
@@ -88,21 +88,20 @@ The built-in image only has a clean Windows or Ubuntu OS and some tools like Git
88
88
* 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);
89
89
* 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.
90
90
3. For the launch method, select SSH or JNLP.
91
-
* Linux agents can be launched only using SSH.
92
-
* 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 Agent or image needs to be custom-prepared with an SSH server pre-installed.
91
+
* For Windows agents, if the launch method is SSH then check Pre-Install SSH in Windows Agent or image needs to be custom-prepared with an SSH server pre-installed.
93
92
94
-
We recommend to use SSH rather than JNLP, for you need less init codes and get much clearer logs.
95
-
> When using the JNLP launch option, ensure the following:
93
+
We recommend to use SSH rather than connecting it to the controller, it's simpler to setup and get much clearer logs.
94
+
> When using the Inbound agent launch option, ensure the following:
> * The URL needs to be reachable by the Azure agent, so make sure to configure any relevant firewall rules accordingly.
98
-
> * TCP port for JNLP agent agents (Manage Jenkins -> Configure Global Security -> Enable security -> TCP port for JNLP agents).
99
-
> * 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.
97
+
> * TCP port for Inbound agents (Manage Jenkins -> Configure Global Security -> Enable security -> TCP port for inbound agents).
98
+
> * The TCP port needs to be reachable from the Azure agent launched with connecting to the controller. It is recommended to use a fixed port so that any necessary firewall exceptions can be made.
100
99
>
101
-
> If the Jenkins controller is running on Azure, then open an endpoint for "TCP port for JNLP agent agents" and,
100
+
> If the Jenkins controller is running on Azure, then open an endpoint for "TCP port for Inbound agents" and,
102
101
> in case of Windows, add the necessary firewall rules inside virtual machine (Run -> firewall.cpl).
103
102
104
-
4. 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.
105
-
We prepared a sample script for Linux via SSH, Windows via SSH and Windows via JNLP. Please find details in help button.
103
+
4. 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 aware you need to at least install JRE if the image does not have Java pre-installed.
104
+
We prepared a sample script for Linux via SSH, Windows via SSH and Windows via connecting to the controller. Please find details in help button.
106
105
107
106
If you hit the [storage scalability limits](https://docs.microsoft.com/en-us/azure/storage/storage-scalability-targets) for your custom images on the storage account where the VHD resides, you should consider using the agent's [temporary storage](https://blogs.msdn.microsoft.com/mast/2013/12/06/understanding-the-temporary-drive-on-windows-azure-virtual-machines) or copy your custom image in multiple storage accounts and use multiple VM templates with the same label within the same agent cloud.
# TODO look at porting the run as service part of the old script from https://raw.githubusercontent.com/Azure/jenkins/master/agents_scripts/Jenkins-Windows-Init-Script-Jnlp.ps1
0 commit comments