Concourse Release Notes
Nov 9, 2017
Concourse 3.6.0 now requires you to install and manage an external PostgreSQL database (v9.5+). We have enabled an upgrade path to the CloudFoundry Postgres BOSH release for your convenience.
Note: you do not need to follow these instructions if your Concourse deployment already connects to an external PostgreSQL database (v9.5+)
If you have not done so already, upgrade your Concourse to 3.5.0. Concourse 3.5.0 includes a change to the postgres job that moves its data to a new location where the Cloud Foundry Postgres release will detect and upgrade from.
Upload the Cloud Foundry Postgres release to your BOSH director. We have tested this upgrade path with version 20, currently available on bosh.io
Once the release is uploaded, add a reference to the job in your Concourse deployment manifest. You can do this by swapping out the
In the same Concourse deployment manifest, update the ATC properties to explicilty configure the database name and role. These values will vary based on your deployment preferences. You can refer to our changes on the single-vm Concourse manifest as a reference point.
Note that the Postgres DB upgrade must not be combined in the same deployment operation as a stemcell update
Concourse 3.6.0 now requires Garden runC 1.9.0. Make sure you download the appropriate version of Garden runC and recreate your workers.
fly validate-pipelinewill now validate the
configfield on embedded tasks. As a part of this change we have removed support for configuring both
file, which has been depracated.
- Build logs now have timestamps. You can find more about it on the feature post here
- Build page now supports keyboard shortcuts. You can find more about it on the feature post here. There is a known issue where keyboard shortcuts are non-functional on Firefox browsers. This should be fixed in a subsequent release.
- Fixed an issue with pipeline scheduling that would result in high database connection usage.
- Fixed an issue where clicking and dragging on the pipeline view would send you to the job details page.
Sep 25, 2017
- Support for CredHub for external credential management
- BaggageClaim volume creation APIs are now asynchronous
- Parallelized garbage collection. This should make things more durable to a slow worker, and make it harder for containers and volumes to “pile up” when the ATC is out of service briefly (i.e. during a deploy)
- BaggageClaim’s response header timeout is now configurable, which should help those with large images that they’re using for privileged tasks.
- When using groups in pipelines,
flywill now let you know when you forgot to assign a job to a group
flynow prints a URL to your build page when you run
- The fly command for
destroy-teamnow lets you supply the flag
- Jobs with a pending build now have a static halo to better represent its waiting state
flyCLI can now format a pipeline configuration into its ‘canonical form’ using the new
abort-buildcommand can now abort by build ID
- The Semver resource now supports Google Cloud Storage
- The Bosh Deployment resource now uses the latest BOSH CLI
- The Semver resource now supports Server Side Encryption
- The Git resource will now save the committer email to
- The legend on the pipeline page will now auto-hide after 10 seconds.
- When switiching between pipelines, the UI will now fit the pipeline in view.
- You can also press 'F’ center a pipeline in view.
- Jobs and resources with a forward slash in their name no longer error out when loading their details.
- Fixed a leak with goroutines that happens from
- Check containers will no longer be brutally destroyed if they’re used too close to their expiration time.
- Previously, if a resource or resource type was parameterized via a credential manager, its check containers and caches would be mistakenly garbage-collected. They will now be kept around.
- Fixed an issue where the pipeline view will reset after a state change on the pipeline.
- Added the appropriate headers to stop GitHub from caching badges
- Fixed an issue with the garbage collector that happens when deleting teams
- Files with the
setgidpermissions set on them will no longer have them removed. This used to be lost with the
chownperformed for namespacing the files. We’ll now restore it after the
- The flags for configuring GitLab oAuth are now present in
- Fixed an underflow in BaggageClaim’s volume size detection
unpackparameter in S3 resource will no longer load the entire archive into memory, so it can be used for larger archives
- A migration introduced in
v3.3.0would load all the builds into memory and then process them, causing a lot of issues when upgrading. We optimized this migration to migrate build plans in batches, rather than all at once.
July 31, 2017
Concourse for PCF is the first version of Concourse that is eligible for Pivotal Support. Concourse v3.3.3 was selected for this release because it addresses crucial issues from the Concourse for PCF tile beta program. Some of the new features in this version are:
- Major changes to the lifecycle management of workers, containers and volumes. For more details please refer to issue #629
- Support for web hooks
- Pipeline config and team auth settings can now be encrypted in the database. See Encrypting Concourse Databases
- Workers now use
btrfsfor their filesystems. For more details please refer to issue #1045
- New templating syntax for pipeline parameterization. See Using ((parameters))
- Performance and stability enhancements from schema optimizations, and parallelized ATC garbage collection
- Credential Management with Vault
- Support for GitLab oAuth configurations
- …and so much more! For a full history of features please visit the official Concourse Release Notes
- Misc bug fixes and stability improvements
- For a full history of bug fixes and known issues please visit the official Concourse Release Notes
- Operators may encounter memory issues on the ATC while upgrading from a version of Concourse older than 3.3.0.