Managing CI Configurations At Scale - Globality

Intro

You often hear about scale issues when discussing capacity, traffic, users and other resource related topics and issues. However, scale is often in the details, the processes and how things run at specific companies.

At Globality, we have ~80 micro-services running in production. We have FE, BE and Gateway applications. JS, Python and third party apps. Most applications also require internal libraries to run.

All of this needs to be built, tested and deployed.

We use CircleCI for everything, but Travis or any other SAAS based CI will have the same common concepts, it's a configuration file that exists inside the project source code and contains instructions on how to build, test and deploy the project.

Even before we had 80 services, we had significant pain with this concept, maintaining those files, changing/adding things to the build process was a huge pain.

Imagine you have to edit 80 files in 80 repos every time you want to add a feature to your build process. Say you want to annotate grafana for every release. Can you imagine that?

... Read the rest on https://www.kensodev.com/posts/2018/08/22/generating-ci-configurations-at-scale