1 About

Concourse started as a side-project by @vito (hi!) and @xoebus in 2014. Since then, Concourse has grown into a small but dedicated team of full-time engineers and part-time contributors.

1.1 Why make Concourse?

When working on a sizable project, having a pipeline to reliably test, deploy, and publish the product is crucial for rapid iteration.

But with every CI system we used, we found ourselves constantly dealing with the same old problems: complicated configs hidden in many pages of the web UI, not knowing who changed what & when, managing dependencies and state on the workers, build pollution, annoying UX...

Our project was growing larger, and with every box we checked and for every worker we hand-tweaked, the anxiety of having to do it all over again if something went wrong grew and grew. We started writing software to manage our CI instead of writing the software for the product we wanted to build.

We built Concourse to be a CI system that lets you sleep easier at night. A CI that's simple enough to fully grok and easy to manage as your project grows; in both the complexity of the product and the size of your team. We wanted to build a CI with strong abstractions and fewer things to learn, so that it can be easier to understand and so that Concourse can age gracefully.

1.2 How can I help?

It's pretty hard to write a CI system that makes everyone happy! Concourse is by no means perfect, and it sometimes takes us while to understand a problem space well enough to figure out how it should work in Concourse's puritanical world.

We tend to move slowly rather than tack on feature request after feature request. We are also extremely cautious about anti-patterns and introducing ways for users to shoot themselves in the foot.

Concourse is getting bigger and bigger, and we really appreciate any help we can get. There are many ways to contribute to Concourse; only some of them involve writing code! You help us out by being active in GitHub issues, voting with reactions for issues that matter to you, engaging in discussions while we map out a feature request, hanging out in our forums, writing documentation, coming up with new designs, and of course contributing code!

As a contributor, you can jump on over to Contribute for a more complete list of resources for contributors

1.3 Thanks!

It's been a long journey and we've got a lot of people to thank for our continued success. We are deeply indebted to any and all who help keep this project going, but the heroic effort of the following organizations is worth giving special props.

1.3.1 Pivotal

Concourse wouldn't be what it is today without Pivotal. This goes beyond the sponsorship, which began in early 2015 - without the experiences we had and the practices we learned while working on Cloud Foundry and BOSH, we would have neither the technical experience nor the strong opinions that led to Concourse being born.

Pivotal's sponsorship continues strong into 2018, where we have a team of full-time engineers, PMs, and designers dedicated to pushing Concourse forward.

1.3.2 Stark & Wayne

The Concourse Tutorial by Stark & Wayne is probably the only reason a lot of people were able to learn Concourse. It's a great asset and does its job so well that we've decided to basically just kill our tutorials and delegate to theirs. Thanks to Dr. Nic for writing and maintaining it, and everyone else that has helped out!