2018
Concourse Update (April 9–13)
Concourse v3.11.0 came out today! Go get it: https://concourse-ci.org/download.html#v3110
Concourse Updates (April 2–6)
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.
A renewed focus & community changes
Phew, we’ve been busy for the past couple of months! There’s a lot to give y’all an update on.
Concourse Update (April 19–23)
Hi folks,
Had an interesting week talking to customers about how we might improve their Concourse operations and deployments. More info on that soon!
Concourse Update (Mar 12–16)
Its been a first week in a long time where we were back to full strength and fully co-located. It was nice!
Concourse Update (Mar 5–9)
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.
We’re switchin’ domains.
(UPDATE March 9 @ ~10 AM: The old domain appears to now be hosting a very old snapshot of our website. This is either targeted or part of a phishing scam. Do not go to it.)
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.