Our customer is a major player in providing SaaS applications for Oil and Gas industry. They are based in Nordics and work extensively with large data sets to solve complex problems for their customers. Their applications use Machine Learning, Data Science and AWS Services to solve some of the most difficult tasks, accurately for their customers.
During our discussion with customer CTO we identified following goals:
- Increase effective build capacity of Jenkins server
- Categorize multiple build slaves based on build requirements such as UI, AWS Sam, Docker, Python etc.
- Use different build slaves for different use cases
- Lower overall cost of running Jenkins CI
By utilizing right sizing and spot instances feature of AWS, we implemented following solution:
- Decresed instanace size of Jenkins master to a Small instance
- Updated Jenkins configurations to run all build jobs on Build Slaves
- Used AWS Spot fleet to request and maintain required build capacity. By utilizing Spot instances, we were able to save about 70% on instance cost while still maintaining required build capacity with Spot Fleet.
- Created 2 Spot Fleets with different CPU & memory requirements based on build types:
- First for Node.js, UI builds
- Second for AWS Sam and Docker builds
- This allowed us to maintain different build slave pools for different job types based on project requirements.
This solution used following tool, platforms, services and programming languages:
- Public cloud platform – AWS. Following services are prominently used:
- AWS EC2
- AWS Spot Fleet
- AWS SAM Templates
- Cloud Formation
- AWS Elastic Container Registery
- AWS Elastic Container Service
- Simple Storage Service
- Jenkins – Continuous integration server
- Docker – Containers for Node.js and Python
- AWS SAM CLI – for bulding and packageing Lambda applications for AWS platform
- Programming languages – Node.js, Python
Based on changes implemented with right sizing and spot instances, customer gained following goals:
- Almost 2X increase in Jenkins CI build capacity
- 40% reduction in cost of running JenkinsCI
- No Queued builds due to increased Build Capacity
- Faster build and deployment