Concourse Update (Nov 5–9)

You’ll soon be able to pin versions in Concourse (Photo Credit George Barnett)

Right off the bat I’d like to give a shoutout to Jamie Klassen and his new post about the upcoming feature for pinning resources. You can check it out the new post here:https://medium.com/concourse-ci/resource-page-explained-eb99cf256fb5

I also wanted to mention that the Github Pull Request that was maintained by JT Archie (https://github.com/jtarchie/github-pullrequest-resource) has been officially deprecated.

  1. The official docs for the resource types no longer point to jtarchie/pr for the PR resource. They are pointing to https://github.com/telia-oss/github-pr-resource now.
  2. There will no longer be any maintenance, issues or PRs accepted on the resource.

We also spent some time this week finalizing our plans for the Concourse 2019 roadmap. We’ll be writing it up in a wiki to share with everyone next week, so keep an eye out for another followup announcement!

On to the update:

Pipeline

  • We finally got a deploy going onto our prod environment. Everything broke but hey, its the attempt that matters

API

  • We’re still investigating various options for refactoring and documenting our API. Joshua Winters is on it!

UX

  • Pinning versions on resources. Make sure you read our write-up on it here!

Core

  • Resource v2 and Spatial resource design! Most of that work is currently being done in a feature branch.

Runtime

Operations / K8s

  • In addition to picking up some issues reported by users around helm-deployed concourse in 4.2.1, Topher Bullock is going to try spending his Fridays making / looking at Concourse Helm chart PRs.