2018
Concourse Update (May 22–25)
It was a short week for us here in Canada, but we had a few interesting updates:
Concourse Update (May 14–18)
In case you missed it, I’d encourage you to check out some of the recent posts from Shashwathi Reddy on “My first month on Concourse” and Joshua Winters regarding upcoming changes to our authentication; “Oh, Auth”. We’d love to hear your feedback!
My first month on Concourse
I have been working as Software Engineer with Pivotal for about 3 years now, during which much of my contributions were primarily within Cloud Foundry teams, such as MySQL service, Routing, and UAA. Early this year I rotated onto Concourse team in Toronto and I would like to share my thoughts on why Concourse team does things differently and why they work.
Concourse Update (May 7–11)
Hi folks,
Joshua Winters has spent a lot of time refactoring Concourse so that it can finally support Users. We’re finally at a point where we can share some our work with you, so I’d really encourage you to check out his recent blog post Oh, Auth
Oh, Auth
As most of you know we’ve been working hard on introducing Users into Concourse. Today, I’m excited to share with you some of the changes we’ve made for an upcoming release of Concourse.
Concourse Update (April 30 — May 4)
I’ve gotten some questions about Freedom Friday from some readers after last week’s update. Well it turns out that Topher Bullock wrote a great article about it this week; you read up on it here: FREEdom Fridays
Open Sourcing the Design System for Concourse
This past week a community member reached out to begin work on a PR for a UI change in Concourse. This sparked some conversations within the team about how might we support this, since a lot of our design assets are private.
Freedom Fridays

When I started as anchor of the Concourse team, one of the things I wanted to improve was the human problem of on-boarding new engineers. Concourse is a large project spanning many areas of expertise (distributed systems, container runtimes, functional programming, user experience, etc.) and several Git repos (atc, fly, tsa, baggageclaim, etc.), so ramping up on ALL THE CONCOURSE can be a difficult task for even the most skilled engineers.
Getting Started with Concourse on macOS

If you haven’t checked out Concourse yet, you definitely should! Simple primitives (Resources, Jobs, Tasks), a heavy emphasis on continuous workflows defined by YAML, and an active & growing community are just some reasons why it’s worth taking a look. This is a quick guide to getting an instance running on your machine in minutes.
