How gowthamsirigiri/jenkins_master_slave_autoscaling works
This repository is an architecture blueprint, not an implementation: Jenkins on a Dockerized EC2 master coordinates work, while an EC2 Auto Scaling Group provisions agents to execute jobs. The documented setup covers agent bootstrap and JNLP connectivity, node configuration, and metric-driven scaling. All repository nodes point to README.md; relationships are limited to those described there.
Main entry points: README.md Jenkins master
Components 13
Jenkins control plane
- Jenkins master
README.md - Docker runtime
README.md - Master EC2
README.md - Node configuration
README.md
Agent provisioning
- Scaling metrics
README.md - Auto Scaling Group
README.md - Launch config / template
README.md
Agent execution
- Agent EC2 instances
README.md - Agent bootstrap
README.md - Jenkins agent JAR
README.md - JNLP connection
README.md - Agent job execution
README.md
Other components
- Dev / QA teams
Connections 14
- Dev / QA teams → Jenkins master: access UI
README.md - Docker runtime → Jenkins master: runs
README.md - Master EC2 → Jenkins master: hosts
README.md - Jenkins master → Node configuration: configure nodes
README.md - Launch config / template → Auto Scaling Group: configures
README.md - Auto Scaling Group → Agent EC2 instances: provisions
README.md - Scaling metrics → Auto Scaling Group: triggers scaling
README.md - Agent EC2 instances → Agent bootstrap: runs
README.md - Agent bootstrap → Jenkins agent JAR: downloads
README.md - Agent bootstrap → Jenkins master: downloads from
README.md - Agent bootstrap → JNLP connection: establishes
README.md - JNLP connection → Jenkins master: connects to
README.md - Jenkins master → Agent job execution: coordinates jobs
README.md - Agent job execution → Agent EC2 instances: executes on
README.md