3 Project

Where is everything?

• The Concourse repo is where the main code lives, where the backlog is planned, and where bugs are reported. It is managed by the maintainers team. Another high-level view of the backlog is also available at project.concourse-ci.org

• The RFCs repo is where shiny new features are designed through collaborating in the open and collecting feedback. It is managed by the core team.

• The Docs repo is the source for the website you're reading now! It is managed by the community team.

• The Governance repo holds the source of truth for the project's permission structure and lays the foundation for self-governing teams. It is managed jointly by the community team and the infrastructure team.

• GitHub Discussions are used for support, announcements, sharing ideas, and general discussion.

• The concourse/concourse GitHub wiki contains community-curated lists of tools and tutorials and serves as a knowledge base for Concourse users and operators.

• The Concourse blog features tutorials and updates from the development side.

• The Concourse Discord server is a great place to chat with other contributors.

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.

How can I help?

Concourse is a free and Open Source software project that relies on the contributions of sponsors and volunteers from around the world.

If you're interested in helping out, head on over to GitHub and check out the contributing docs!

Report a security issue

To report a security issue, please send an email to security@concourse-ci.org.

Security advisories will be published as concourse/concourse GitHub Security Advisories and subsequently cross-posted to the Concourse Security mailing list which you may join to subscribe to security updates.

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.

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.

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!