You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Zoe Tian 94f6dd2cd8
Merge pull request #6059 from Pix4D/fly_execute_tags
11 hours ago
.github add in pr feedback 1 month ago
atc Fly execute: pass worker tags to input. 17 hours ago
cmd increase timeout for system claim startup error 2 months ago
fly Fly execute: pass worker tags to input. 17 hours ago
go-concourse Fly execute: pass worker tags to input. 17 hours ago
hack atc: Allow OPA integration to return reasons 1 month ago
release-notes tasks scheduling: metrics: enhance TasksWaiting metric. 1 month ago
screenshots add 2x scaled screenshot for hidpi laptops 2 years ago
skymarshal fix: add EntityIssuer and SsoIssuer flags 3 weeks ago
testflight testflight: prevent pipeline from getting GC'd 1 month ago
topgun Merge pull request #6001 from concourse/issue/5967 2 weeks ago
tracing Merge pull request #5579 from concourse/volume-streaming-tracing 3 months ago
tsa Merge pull request #5845 from concourse/use-concourse-gclient 1 month ago
vars vars: behaviour: properly handle local scope 1 month ago
web skipping benchmarks until dependency is fixed 5 days ago
worker Merge pull request #6031 from concourse/default-pool 1 day ago
.dockerignore flesh out 2 years ago
.env run watsjs/testflight against prebuilt Concourse 2 years ago
.gitignore worker: rename backend to runtime 4 months ago update notice and concourse email 2 months ago contributing: structure: remove newline 2 months ago
Dockerfile Dockerfile: set key env vars after generating keys 5 months ago re-init 2 years ago update notice and concourse email 2 months ago revise 'road to v10' words 1 month ago add 2 months ago
docker-compose.yml Enable garden DNS proxy in docker-compose 1 month ago
go.mod Merge pull request #5955 from concourse/fix-fly-tokens 1 month ago
go.sum bump baggageclaim to v1.8.0 1 month ago
package.json skipping benchmarks until dependency is fixed 5 days ago
tools.go Add tools.go to keep track of tool versions 1 year ago
versions.go concourse/#3819 using zstd to streamIn/Out between workers 1 year ago
webpack.config.js web: babel-ify javascript bundle 6 months ago
yarn.lock build(deps): bump yargs-parser from 13.1.1 to 13.1.2 1 week ago

Concourse: the continuous thing-doer.

Help Wanted

Concourse is an automation system written in Go. It is most commonly used for
CI/CD, and is built to scale to any kind of automation pipeline, from simple to

booklit pipeline

Concourse is very opinionated about a few things: idempotency, immutability,
declarative config, stateless workers, and reproducible builds.

The road to Concourse v10

Concourse v10 is the code name for a set of features which, when used
in combination, will have a massive impact on Concourse’s capabilities as a
generic continuous thing-doer. These features, and how they interact, are
described in detail in the Core roadmap: towards v10 and Re-inventing
resource types
blog posts. (These posts are slightly out of
date, but they get the idea across.)

Notably, v10 will make Concourse not suck for multi-branch and/or
pull-request driven workflows
- examples of spatial change, where the set
of things to automate grows and shrinks over time.

Because v10 is really an alias for a ton of separate features, there’s a lot
to keep track of - here’s an overview:

Feature RFC Status
set_pipeline step #31 ✔ v5.8.0 (experimental), TODO: #5814
Var sources for creds #39 ✔ v5.8.0 (experimental), TODO: #5813
Archiving pipelines #33 ✔ v6.5.0
Instanced pipelines #34 🚧 PR #5896 for backend, issue #5921 for UI
Static across step 🚧 #29 ✔ v6.5.0 (experimental)
Dynamic across step 🚧 #29 🙏 RFC needs feedback!
Projects 🚧 #32 🙏 RFC needs feedback!
load_var step #27 ✔ v6.0.0 (experimental)
get_var step #27 🙏 #5815 Looking for volunteers!
Prototypes #37 ⚠ Pending first use of protocol (any of the below)
run step 🚧 #37 ⚠ Pending its own RFC, but feel free to experiment
Resource prototypes #38 🙏 #5870 Looking for volunteers!
Var source prototypes ⚠ Needs RFC
Notifier prototypes 🚧 #28 ⚠ RFC not ready

The Concourse team at VMware will be working on these features, however in the
interest of growing a healthy community of contributors we would really
appreciate any volunteers. This roadmap is very easy to parallelize, as it is
comprised of many orthogonal features, so the faster we can power through it,
the faster we can all benefit. We want these for our own pipelines too! 😆

If you’d like to get involved, hop in Discord or leave a comment on
any of the issues linked above so we can coordinate. We’re more than happy to
help figure things out or pick up any work that you don’t feel comfortable
doing (e.g. UI, unfamiliar parts, etc.).

Thanks to everyone who has contributed so far, whether in code or in the
community, and thanks to everyone for their patience while we figure out how to
support such common functionality the “Concoursey way!” 🙏


Concourse is distributed as a single concourse binary, available on the Releases page.

If you want to just kick the tires, jump ahead to the Quick Start.

In addition to the concourse binary, there are a few other supported formats.
Consult their GitHub repos for more information:

Quick Start

$ wget
$ docker-compose up
Creating docs_concourse-db_1 ... done
Creating docs_concourse_1    ... done

Concourse will be running at You can
log in with the username/password as test/test.

Next, install fly by downloading it from the web UI and target your local
Concourse as the test user:

$ fly -t ci login -c -u test -p test
logging in to team 'main'

target saved

Configuring a Pipeline

There is no GUI for configuring Concourse. Instead, pipelines are configured as
declarative YAML files:

- name: booklit
  type: git
  source: {uri: ""}

- name: unit
  - get: booklit
    trigger: true
  - task: test
    file: booklit/ci/test.yml

Most operations are done via the accompanying fly CLI. If you’ve got Concourse
installed, try saving the above example
as booklit.yml, target your Concourse
, and then run:

fly -t ci set-pipeline -p booklit -c booklit.yml

These pipeline files are self-contained, maximizing portability from one
Concourse instance to the next.

Learn More


Our user base is basically everyone that develops software (and wants it to

It’s a lot of work, and we need your help! If you’re interested, check out our
contributing docs.