Skip to content

Blog

  • 3 min read

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!).

  • 4 min read

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.

  • 6 min read

Designing for Space in Concourse

This feature is still in the early stages of development. We are picking up from our previous sneak peak post by James Ma. If you have a comment and want to participate in the conversation please visit the issue on GitHub.

Concourse Pipeline Engineers have been asking for a better way to test variations and combinations of a resources in their pipelines. When pipelines are composed of resources that duplicate themselves to account for product versions (semver), branches of a repo, and different environments, the resulting pipeline can be quite difficult to navigate and edit.