70a4d75520 | ||
---|---|---|
.. | ||
README.md | ||
azuredeploy-parameters.json | ||
azuredeploy.json | ||
jenkAddNode | ||
jenkMstrInstall.sh | ||
jenkSlaveInstall.sh | ||
jenkmaster-resources.json | ||
jenkslave-resources.json | ||
metadata.json | ||
shared-resources-parameters.json | ||
shared-resources.json |
README.md
Install a Jenkins Master and Slave node on Ubuntu Virtual Machines using Custom Script Linux Extension
This template deploys a Jenkins master node on an Ubuntu virtual machines and multiple Jenkin slave nodes on two additional VM. This template also provisions a storage account, virtual network, availability sets, public IP addresses and network interfaces required by the installation.
The example expects the following parameters:
Name | Description |
---|---|
storageAccountPrefix | Unique DNS Name for the Storage Account where the Virtual Machine's disks will be placed (multiple storage accounts are created with this template using this value as a prefix for the storage account name) |
adminUsername | Admin user name for the Virtual Machines |
adminPassword | Admin password for the Virtual Machine |
region | Region name where the corresponding Azure artifacts will be created |
virtualNetworkName | Name of the Virtual Network that is created and that resources will be deployed in to |
dnsName | The domain name portion of the publicly accessible Jenkin master {domainName}.{region}.cloudapp.azure.com (e.g. mydomainname.westus.cloudapp.azure.com) |
masterVmSize | The size of the Jenkins Master node VM. Default = Standard_D3 |
slaveVmSize | The size of the Jenkins slave node VM(s). Default = Standard_D3 |
slaveNodes | The number of Jenkins Slave nodes. Default = 1 |
Topology
This template deploys a Jenkins master and a configurable number of Jenkins slave nodes.
The master node is exposed on a public IP address that you can access through a browser on port :8080 as well as SSH on the standard port.
##Known Issues and Limitations
- The template does not currently configure SSL on master or slave nodes.
- The template uses username/password for provisioning and would ideally use an SSH key
- The deployment scripts are not currently idempotent and this template should only be used for provisioning a new master and slave.