Your pipeline is then visualized in the web UI, taking only one click to get from a failed job to seeing why it failed.
The visualization provides a "gut check" feedback loop: if it looks wrong, it probably is wrong.
A more complicated example...
Jobs can depend on other jobs by configuring passed constraints. The resulting chain of jobs and resources is a dependency graph that continuously pushes your project forward, from source code to production.
All configuration and administration is done using the fly CLI.
The fly set-pipeline command pushes the config up to Concourse. Once it looks good, you can then check the file in to source control. This makes it easy to recover your project if the Concourse server burns down.
Reproducible, debuggable builds
$ fly -t ci intercept -j booklit/unit -s unit
PID TTY TIME CMD
171 pts/1 00:00:00 bash
1876 pts/1 00:00:00 ps
Everything runs in containers, ensuring a clean environment on every run.
Each task specifies its own image, giving it full control over its dependencies, rather than managing packages and state on your workers.
The fly intercept command will pop you right into one of your build's containers, making it easy to troubleshoot flaky builds.
The fly execute command lets you run a build with local changes.
This build runs in exactly the same way as it would run in your pipeline, without having to push broken commits until it works.
When a build in the pipeline fails, you can run fly execute with the -j flag to run a one-off build with the same inputs as the failed build. You can then replace an input with your local changes with -i to see if your fix is valid.
Concourse does not have a complex plugin system. Instead, it focuses on a single strong abstraction: resource, which are implemented by resource types.
The pipeline.resources field configures external artifacts that your pipeline will monitor for changes, fetch from, and push to.
For example, a resource with type git refers to a git repository, which will be cloned in a get step and pushed to using a put step. Behind the scenes, Concourse will continuously run git fetch to look for new commits that jobs may want to trigger on.
At its core, Concourse knows nothing about git. It comes with a git resource type out of the box, but you could just as easily bring your own into your pipeline by setting the pipeline.resource_types field.