Concourse Update (Sept 03 — Sept 07)
“Disco” Dirk Nowitzki approves of release 4.1
Blog
Concourse Build Page Explained
Continuing on our Concourse UI Explained series, this week we are taking a look
at a Concourse job’s build page. As always, we will be using
our production pipeline as a guide to connect the mapping of an element to their meaning
and purpose.
Concourse Update (Aug 27–31)
Photo courtesy of the CNE
Concourse Update (August 20–24)
Logs and resources
Concourse Resource Volume Caching
This is a follow-up to James Ma’s post on “Suspicious Volume Usage on Workers”. James also helped out with the illustrative diagrams for this post!
Concourse Update (August 13–17)
Combining repos for great justice
Concourse Pipeline UI Explained
The Concourse UI is continuously growing and improving, and the goal of this article is to surface the latest design elements of the Concourse UI. Using our production pipeline, it will become easier to connect the mapping of an element to its meaning and purpose.
PSA: The Great Code Restructuring of 2018
Hi y’all!
As anyone trying to contribute will have probably noticed by now, we have a bunch of repos, and most of them are
inter-dependent. This makes it difficult to contribute PRs, because you’ll often have to PR to fly, go-concourse,
and atc and cross-reference them. But then each of their builds will fail because they won’t have their dependent
changes (e.g. fly will fail until go-concourse is merged and bumped, but go-concourse's build will fail until
atc is merged and bumped, which we don’t want to do because the other builds are failing!).
Suspicious Volume Usage on Workers
As a Product Manger at Pivotal I’m often called on to help with our customer’s Concourse-related issues. I recently spent some time hunting down an issue around suspiciously high volume usage on Concourse workers. It was an interesting problem that I wanted to share with the broader Concourse community.