Skip to content

Blog

Concourse Update (Feb 26 — Mar2)

After some wrestling with our production pipelines last week we managed to release a patch update in the form of Concourse v3.9.1. We’ve fixed some of the reported bugs from the previous release (3.9.0) so definitely go and check it out!

I don’t have much else regarding updates this week so here’s a fun fact for you to chew on: did you know that Concourse uses Concourse to deploy Concourse? Its true! You can check out our publishing pipelines here: https://ci.concourse-ci.org/teams/main/pipelines/main?groups=publish

Concourse Update (Feb 20–23)

Monday, Feb 19 was Family Day for us here in Canada, so its been a relatively short work week for the Concourse team. With the release of v3.9.0 last week, we’ve gotten some reports of new bugs and issues, so thanks to everyone who reported them in via our GitHub issues and Slack. Please make sure to check the updated release notes (here) for the full details! We’re planning to cut a new patch release early next week with some of the fixes to the reported issues.

Concourse Updates (Jan 29 — Feb 2, 2018)

As a Product Manager at Pivotal, one of my responsibilities is to write weekly updates to let Pivots know what the Concourse team has been up to for the past week. When the Concourse team got together earlier this month for our 2018 planning, we decided that we should be sharing these updates with our community as a whole. So, without further ado, here’s our first update of 2018!

Designing a Dashboard for Concourse

With the growing popularity of Concourse, we noticed that our development teams wanted to observe and monitor multiple pipelines simultaneously. This behavior wasn’t limited to just Pivotal engineering teams; in fact, it was even more prevalent amongst our Open Source Community. Our users currently solve this by cramming multiple browser windows into TV their monitor view, or they use the Concourse Summary (aka Crystal) by David Goddard of the Pivotal Buildpacks team.

Earning our Wings

In April 2017 the Concourse Crew set up a large BOSH deployment of Concourse for internal use across Pivotal; we called this shared instance “Wings”. We started on this endeavor to iterate and improve on Concourse as a large scale multi-tenant CI/CD solution, to drive out new features and to validate the Pivotal supported BOSH release of Concourse.