How azure/jenkins works
Project type and purpose
• This is an Azure “Solution Template” repository that defines infrastructure-as-code (IaC) for deploying a Jenkins master on a Linux VM within Azure, plus accompanying artifacts for:
• Initializing Windows-based Jenkins agents via PowerShell
• Disaster-recovery guidance
• “Quickstart” blue-green or rolling-update pipelines targeting either AKS or VM Scale Sets
File structure
• Top-level folders:
• solution_template/ & solution_template_fairfax/ – ARM JSON templates, UI definition, parameter files, nginx web page assets, install scripts
• agents_scripts/ – PowerShell scripts (JNLP & SSH) and XML configs for bootstrapping Windows Jenkins agents
• quickstart_templates/ – subfolders for shared credentials and zero-downtime deployment (kubernetes & vmss)
• disaster_recovery/ – markdown doc describing DR steps
• Key IaC artifacts: mainTemplate.json, createUiDefinition.json, parameter files (publicIP, VM, vnet), ARM-linked custom script extensions (install_jenkins.sh, install-web-page.sh)
• Deployment scenarios: single Linux VM + nginx front end, optional AKS cluster or VMSS for blue/green or rolling updates
Extract additional architecture insights from the README
• Azure Marketplace template deploys an Ubuntu VM, installs Jenkins and plugins
• Windows VMs can be auto-provisioned as agents via the provided scripts
• Quickstart pipelines use Azure CLI, kubectl, Packer for image baking and deployment orchestration
a. Main components
• Azure Resource Manager (ARM) orchestration
• Resource Group containing:
– Virtual Network & Subnet
– Network Security Group (firewall rules)
– Public IP & optional Load Balancer
– Linux VM (Ubuntu) running Jenkins master
– nginx web server (optional front end)
– Windows VMs (as Jenkins agents)
– (Optional) AKS cluster or VM Scale Set for application deployment
• External: users (DevOps engineers), Azure Marketplace, Azure Storage (for ARM scripts & images)
b. Relationships & interactions
• ARM template → provisions all Azure resources
• Jenkins master ← uses Custom Script Extension to run install_jenkins.sh
• Jenkins UI served via nginx or directly on VM’s public endpoint
• Jenkins master → spawns agent processes on Windows VMs (PowerShell scripts via JNLP/SSH)
• Jenkins jobs → call Azure CLI, kubectl or Packer to deploy apps to AKS/VMSS
• Disaster recovery guide interacts with Azure Backup or snapshotting of VM disks
c. Architectural patterns & principles
• Declarative IaC (ARM JSON)
• Separation of control plane (ARM) vs. data plane (VM workloads)
• Blue-Green and Rolling Update strategies encapsulated in quickstart pipelines
• Extensibility: agent bootstrap scripts can be swapped out or extended
d. Core technologies & frameworks
• Azure Resource Manager (mainTemplate.json, parameter files)
• Azure Marketplace solution template conventions
• Bash scripts, PowerShell scripts, Custom Script Extension
• nginx for static content or reverse proxy
• Jenkins (master/agent architecture)
• Kubernetes (AKS) or VM Scale Set for zero-downtime deployments
• Packer (for VMSS image baking)