Go to file
Taylor Silva c0523c3942
Merge pull request #8687 from konstl000/master
add shared path to SSM parameters
2023-11-30 12:49:44 -05:00
.github fix mpb compilation error; stick to yaml.v2 2023-10-17 21:15:58 -04:00
atc Merge pull request #8687 from konstl000/master 2023-11-30 12:49:44 -05:00
cmd refactor: move from io/ioutil to io and os packages 2023-06-18 16:54:49 +08:00
fly fix mpb compilation error; stick to yaml.v2 2023-10-17 21:15:58 -04:00
go-concourse chore: unnecessary use of fmt.Sprintf or fmt.Sprint 2023-07-06 16:15:05 +08:00
hack rotate vault certs for dev 2022-07-25 17:10:48 -04:00
integration fix integration flaky ops test 2023-10-10 12:45:21 -04:00
screenshots add 2x scaled screenshot for hidpi laptops 2018-09-19 10:36:30 -04:00
skymarshal Fix atc panic error due to missing robots.txt for dex server. 2023-09-19 12:36:40 -07:00
testflight refactor: move from io/ioutil to io and os packages 2023-06-18 16:54:49 +08:00
topgun manually major version bumps of libs 2023-10-16 22:35:49 -04:00
tracing test: update references to use ginkgo/v2 2023-03-10 17:33:13 -05:00
tsa fix mpb compilation error; stick to yaml.v2 2023-10-17 21:15:58 -04:00
vars test: update references to use ginkgo/v2 2023-03-10 17:33:13 -05:00
web chore(deps): update javasript 2023-10-01 00:34:40 +00:00
worker bump txn2/txeh to v1.5.4 2023-09-13 20:27:29 -04:00
.agignore remove baggageclaim CI code 2021-08-16 14:05:11 -04:00
.deepsource.toml add deepsource config 2020-10-02 11:28:28 -04:00
.dockerignore don't rebuild on changes to docker-related files 2021-03-19 09:51:37 -04:00
.env run watsjs/testflight against prebuilt Concourse 2018-10-01 17:10:35 -04:00
.gitignore integration: re-add docker-compose.yml 2021-01-28 17:08:18 -05:00
CODE_OF_CONDUCT.md bump CoC to 2.0, use @concourse-ci.org emails 2021-05-20 13:49:11 -04:00
CONTRIBUTING.md Update path for example pipeline 2022-10-18 19:31:01 -07:00
Dockerfile bump to go 1.17 in go.mod and add goproxy in dockerfile 2022-01-06 10:45:52 +08:00
LICENSE.md re-init 2018-09-18 15:26:17 -04:00
NOTICE.md update notice and concourse email 2020-07-09 12:24:23 -04:00
README.md Fix 404 links to blog posts 2023-08-17 14:35:45 +02:00
SECURITY.md bump CoC to 2.0, use @concourse-ci.org emails 2021-05-20 13:49:11 -04:00
docker-compose.yml clean up 2023-03-16 14:11:47 +08:00
go.mod fix mpb compilation error; stick to yaml.v2 2023-10-17 21:15:58 -04:00
go.sum manually major version bumps of libs 2023-10-16 22:35:49 -04:00
package.json chore(deps): update javasript 2023-10-01 00:34:40 +00:00
tools.go goimports all files 2021-10-08 12:50:28 -04:00
versions.go Support "nozip" for volume streaming. 2023-03-14 11:44:44 +08:00
webpack.config.js web: babel-ify javascript bundle 2020-02-28 09:56:22 -05:00
yarn.lock chore(deps): update javasript 2023-10-01 00:34:40 +00:00


Concourse: the continuous thing-doer.

Discord Build Contributors 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 complex.

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)
Var sources for creds #39 ✔ v5.8.0 (experimental), TODO: #5813
Archiving pipelines #33 ✔ v6.5.0
Instanced pipelines #34 ✔ v7.0.0 (experimental)
Static across step 🚧 #29 ✔ v6.5.0 (experimental)
Dynamic across step 🚧 #29 ✔ v7.4.0 (experimental, not released yet)
Projects 🚧 #32 🙏 RFC needs feedback!
load_var step #27 ✔ v6.0.0 (experimental)
get_var step #27 🚧 #5815 in progress!
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 🚧 #6275 planned, may lead to 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 https://concourse-ci.org/docker-compose.yml
$ 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.

⚠️ If you are using an M1 mac: M1 macs are incompatible with the containerd runtime. After downloading the docker-compose file, change CONCOURSE_WORKER_RUNTIME: "containerd" to CONCOURSE_WORKER_RUNTIME: "houdini". This feature is experimental

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: "https://github.com/vito/booklit"}

- 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 instance, 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 work).

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