GitLab CI and Distributed Builds
HumanGeo switched from Jenkins to GitLab and cut costs by 1/3

HumanGeo switched from Jenkins to GitLab and cut costs by 1/3

11/14/2017 · William Chia

What this post added

HumanGeo migrated from Jenkins to GitLab CI, reducing CI administration time from 5-6 hours/month to 10-15 minutes/month. They achieved approximately 1/3 cost savings by utilizing GitLab's flexible CI runners with autoscaling on spot instances for ~40 hours/week, compared to a dedicated m2.xlarge instance on AWS for Jenkins. The adoption of GitLab CI's YAML DSL for defining CI as code was highlighted as a significant ease-of-use improvement over Jenkins' Groovy.

Read the original post ↗