Containerized Jenkins

After careful planning, the Luneba team decided to use the ECS cluster with Fargate services that run in separate VPC in hub-and-spoke network. Jenkins master node is running as Fargate service, build agents run as short-living tasks.

One challenge the team faced was that Windows containers could not be run on Fargate as tasks, so we had to manage ECS container instances outside of the ECS cluster as EC2 instances. EC2 Autoscaling was used to autoscale these instances as needed. However, this did not impede the ability to run containerized Windows agents on Jenkins.

We also chose to use Nginx as a reverse proxy to pass webhook requests from GitHub to Jenkins. Fargate service runs Nginx as long-living tasks.

To manage the infrastructure, the team used CloudFormation templates. To implement a reliable application, Jenkins master node configuration is kept in YAML files and build data is kept in shared EFS storage.

Overall, Luneba was able to successfully implement the client’s cloud-native Jenkins environment that was integrated with GitHub and it is now running smoothly. The cost of usage corresponds to the Pay-As-You-Go model, so the client is able to easily manage and control their costs.