This release has issues. Primarily with the BOSH distribution. You should probably just skip straight to v3.8.0.
We've ripped out the old & janky PostgreSQL job from our Concourse BOSH release. You will have no choice but to bring your own PostgreSQL database.
We've changed how we develop database migrations, so as to support down migrations in the future. This will hopefully mean that if you upgrade Concourse and for whatever reason need to back out, you'll be able to, instead of being stuck on a (possibly broken) latest version.
As part of this switch, we've also squashed our migrations into one big bang, which should also improve startup time for fresh installations. However, this means that you must first upgrade to v3.6.0 before upgrading to v3.7.0!
So, do that. You may need to anyway now that we've removed PostgreSQL (see previous note).
There are new required manifest changes to deploy this release with BOSH.
Our BOSH release used to have a few magical mystical packages called
generated_something. These packages would generate a RSA key every time they compiled, in service of automagically wiring up security credentials so you didn't have to put them in your manifest.
This approach was extremely clever and whoever came up with the idea was a downright genius, way ahead of their time.
We've now collectively decided that the whole approach is stupid and redundant now that BOSH manifests can generate their own typed variables. It was fun while it lasted.
As an alternative to hand-editing your manifest, the next release note may pique your interest.
We have started dusting off
concourse-deployment and using it as a central location for Concourse BOSHy deployment goodness. We now use it for our production deployment, as well as a few testing environments. We've updated the Clusters with BOSH documentation accordingly.
We are now openly gathering feedback on one of our worst-kept-secrets: the Concourse dashboard view. You can access it by visiting
In this version of Concourse, we've tweaked some of the visual elements of the dashboard to make it more readible for installations with multiple teams. We've also fixed some of the pipeline states so that they make more sense.
Tell us what you think about the new dashboard by dropping us a line on #1829.
execute command will now default to
-x, which has been replaced with a new flag,
--include-ignored, to revert to the old behavior.
In addition, Fly will no longer blow up when trying to execute with an input that doesn't have a
.gitignore. It will also not blow up if any inputs are files and not directories.
The ATC will now use a separate database connection pool for the API and the pipeline scheduling work. This will make it so that a bunch of slow API requests can't starve critical functionality.
Pipeline-provided resource types will no longer fail miserably for a minute or two when they're first configured.
You can now specify a
on_abort hook on a step or on a job. It will run on abort.
The ATC can now be configured with a pure-random worker selection strategy, which may help users affected by our default resource affinity placement, which can result in overloaded workers. This is thanks to a PR by @phillbaker!
To use the random placement strategy, pass
--container-placement-strategy=random to the
Teams can now have BitBucket-based auth, thanks to a PR by @SHyx0rmZ!
Inline task configs are now validated as part of pipeline validation, thanks to a PR by @jmcarp!
Notice how this note and the prior note have entirely different property names for doing the same thing. Blargh! See #1027.
ATC now has a flag for using k8s secrets when running in a cluster. This change makes using the k8s credential manager an explicit choice when running inside k8s, and also allows you to use a different credential manager when running in a cluster. Thanks for the PR and the patience by @william-tran and @farcaller
When the ATC is configured with multiple metrics emitters, it will now error, rather than silently picking one, thanks to a PR by @jmcarp.
Fixed an issue where selecting/copying the build output would also select the timestamp on the left.
fly login will now error if arguments are mistakenly given to it.
Turns out you could easily spam the build page by holding
T to trigger multiple builds. We've fixed that now so it only triggers a build once. #YOTO
Fixed the web UI so that it appropriately shows that you are logged out when your session expires.
Fixed an issue with the CredHub integration that made it necessary to configure
--insecure-skip-verify, thanks to a PR by @aeijdenberg!