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.
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.
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.
Concourse v3.11.0 came out today! Go get it: https://concourse-ci.org/download.html#v3110
If you haven’t done so already please check out Alex Suraci’s recent update post on “A renewed focus & community changes”. It covers all the recent changes that we’ve been making; starting with the new styling of the website, our new discussion forum, and our migration to Discord chat.
Phew, we’ve been busy for the past couple of months! There’s a lot to give y’all an update on.
Hi folks,
Had an interesting week talking to customers about how we might improve their Concourse operations and deployments. More info on that soon!
Its been a first week in a long time where we were back to full strength and fully co-located. It was nice!
Whelp, that felt like a long week. If you haven’t heard the news by now you should definitely read Alex Suraci’s post regarding our domain.
