Jenkins operation cost is wasteful, so we should use CI services
If you’re in a situation where engineering development resources are insufficient, the operational cost of Jenkins is wasteful, so you should use CI services like CircleCI.
Jenkins vs CircleCI Advantages and Disadvantages
The following articles are helpful for understanding the advantages and disadvantages of Jenkins and CircleCI.
Don't spend operational costs on Jenkins, use CI services instead
Jenkins Disadvantages
- Need to build a server for Jenkins
- Tends to become person-dependent (Jenkins craftsman)
Building, operating, and customizing Jenkins servers consumes engineering resources.
Especially for startups and small-to-medium enterprises, I think engineering resources are insufficient, so they can’t afford to allocate resources to Jenkins itself. If you have such resources, you should allocate them to developing your own services.
And paying for CI services like CircleCI will be cheaper compared to engineer labor costs.
CircleCI is free for one container, and it costs $50 for each additional container, which is quite cheap compared to engineer labor costs.
Conclusion: Use CI Services
Companies with engineer shortages should use external CI services like CircleCI instead of Jenkins and focus on developing their own services.
That’s all from the Gemba where I want you to use CI services instead of Jenkins.
References
In this article, I recommended CircleCI which is free to start with, but there are many other CI services, so it would be good to use an appropriate CI service by referring to the following articles.