Continuous integration
What is Concourse CI? An introduction to the Concourse CI Project's open-source automation system
Concourse CI is an open-source automation system built on resources, tasks, and jobs, and it is suited to CI/CD. Its documentation likens a pipeline to a distributed, continuous Makefile. Everything runs in containers, so each run starts in a clean environment.
- Tool
- Concourse CI
- Made by
- Concourse CI Project
- Official site
- concourse-ci.org
- Category
- Continuous integration
Who makes Concourse CI
Concourse CI is made by the Concourse CI Project.
The official website is linked below.
Official website: concourse-ci.org
What Concourse CI is for
Concourse CI is used to define and run CI/CD pipelines from three building blocks: resources, tasks, and jobs. Each job has a build plan that defines its input resources and the actions to take. Jobs can depend on other jobs, which forms a dependency graph.
Pipelines are visualized in the web UI, which helps in finding the cause of a failure. Configuration and management are done through the fly CLI, and pipeline configuration can be kept in source control.
Who Concourse CI is for
The project does not state a specific audience. Based on its design, it suits teams that want pipelines defined as configuration in source control and executed in containers.
Teams that prefer resources and resource types to a complex plugin system will find that approach fits the model.
Notable capabilities
Concourse CI emphasizes a small set of concepts, container isolation, and CLI-driven debugging. The capabilities below are those the project states.
- Pipelines are built from resources, tasks, and jobs.
- Jobs have build plans and can depend on other jobs, forming a dependency graph that is visualized in the web UI.
- The fly CLI handles configuration and management.
- Fly intercept gives direct access to a build's containers for debugging.
- Fly execute runs builds with local modifications.
- Resources and resource types are used rather than a complex plugin system, with a git resource type included by default and support for adding custom resource types.
- Tasks run in containers that provide some isolation from the host.
- With the containerd runtime, options exist to reduce container escape risk from privileged tasks.
How Concourse CI fits continuous integration
In the continuous integration category, Concourse CI is a pipeline system where inputs, outputs, and dependencies between jobs are explicit. Running everything in containers gives each run a clean environment, which keeps builds from depending on leftover state.
In Deployelm's wider niche of CI/CD and deployment platforms, it is an open-source option that is configured through the fly CLI and kept in source control. Its debugging tools, fly intercept and fly execute, are aimed at shortening the loop when a pipeline fails.
Frequently asked questions
What is Concourse CI used for?
Concourse CI is used for CI/CD. Pipelines are built from resources, tasks, and jobs, and everything runs in containers.
What is the fly CLI in Concourse CI?
Fly is the CLI used for configuration and management of Concourse CI. It also provides fly intercept for accessing a build's containers and fly execute for running builds with local modifications.
Is Concourse CI open source?
Yes. Concourse CI is open source.
Does Concourse CI use plugins?
It uses resources and resource types rather than a complex plugin system. A git resource type is included by default, and custom resource types can be added.
How does Concourse CI handle container security?
Tasks run in containers that provide some isolation from the host. With the containerd runtime, options exist to reduce container escape risk from privileged tasks.
Deployelm is independent and is not affiliated with Concourse CI Project. Product names belong to their owners. Features change; confirm details on the official website.