/JenkinsECS

We want to make a scalable , recoverable Jenkins build cluster which does its capacity planning according to the scalability rule that we define during creation. What it means is we are trying to make a build pipeline which does its own capacity planning, will take minimum manual effort to setup/recover and is leveraging the cloud services of AWS. There are 2 ways to go about it, as suggested in the AWS White paper linked in the reference section. First, the traditional deployment on top of Amazon Elastic Compute Cloud (Amazon EC2) barebone machines. This approach is just like installing Jenkins on a local server, it comes with the traditional pros and cons. The second is the containerized deployment that leverages Amazon EC2 Container Service (Amazon ECS). Using an extensive plugin system, Jenkins offers options for integrating with many AWS services and can morph to fit most use cases (e.g., traditional development pipelines, mobile development, security requirements, etc.). While the white paper suggests using EFS in a containerized system, we are going to work around it because of the region we are in (ca-central-1)

Primary LanguageShell

This repository is not active