How We Build Concourse
Building on some of our previous posts on the Concourse team mechanics1, I wanted to spend some time going over how we actually build Concourse.
Building on some of our previous posts on the Concourse team mechanics1, I wanted to spend some time going over how we actually build Concourse.
Before diving into the weeds of Concourse architecture, let’s briefly take a look at container and volume lifecycles in Concourse. Going forward in this post I will refer to container and volume together as a “worker resource”. In the current architecture, there are multiple ways for worker resource creation to be triggered; like when jobs are started in pipelines or checking for a newer version of a resource. The ATC is responsible for managing worker resource lifecycle like creating, transitioning and destroying them. Workers are designed to be dumb and follow the orders issued by ATC. Removal of worker resource on worker and its reference (in ATC) is done as part of Garbage collection (GC) process in ATC.
It was a short week for us here in Canada, but we had a few interesting updates:
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!
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.
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
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.
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
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.