Hey, this blog post is the continuation of the previous post (How to build and run Concourse CI locally). In this one, I try to understand better how one of its main components works internally to keep track of pipelines and have builds triggered. Let’s dig into what goes on when a pipeline is submitted to Concourse. The API As a consumer of the “concourse service”, the API server is the first point that we touch. The API server in this case is atc: From the words of the atc repository:...
