Scale up your Jenkins master by running Jenkins slave agents in AWS!
Eventually your Jenkins master will reach capacity. The best way to horizontally scale your continuous integration setup is to run your jobs outside of the Jenkins master, in their own slave agents.
In this video I'll show you step-by-step how to set this up in AWS, using a plugin which integrates with the container orchestration framework AWS ECS (Elastic Container Service).
▶️ Installing the Amazon ECS Jenkins plugin
1:49
▶️ Plugin configuration overview
3:03
▶️ Plugin configuration in Jenkins
4:20
▶️ Creating and running a Jenkins job
12:24
▶️ Troubleshooting tips
14:19
Resources you might find helpful
✅ Here's the article I mention in the video, with all the plugin configuration values you need for a basic setup. It also has a CloudFormation stack to create your own Jenkins master + all the AWS resources I reference in the video https://tomgregory.com/jenkins-jobs-in-aws-ecs-with-slave-agents
✅ Here's the documentation for the amazon-ecs Jenkins plugin. It's got a lot of useful information, like what IAM permissions your Jenkins master will need in order to create the slave agents https://github.com/jenkinsci/amazon-ecs-plugin
✅ If you want to take things one step further, see this article about automating the manual process from this video using Jenkins Configuration as Code https://jenkinshero.com/using-jenkins-configuration-as-code-to-setup-aws-slave-agents-automatically
Let me know how you get on :)