Skip to content

v3.12.0
Compare
Choose a tag to compare
@vito vito released this 25 Apr 16:28
v3.12.0
9385d5d

warning: A bug was introduced in build-reaper under ATC/web that causes old build logs to accumulate in Concourse (#2187).

warning: Jun 1, 2018 A bug in Chrome 67 causes it to crash when loading the Concourse UI. At the time of this notice, the dev/canary versions of Google Chrome should work, as well as other browsers like Firefox and Safari. You can follow along the issue in #2236

feature, breaking

  • The ATC will now batch-delete containers and volumes, rather than making individual calls out to the worker. This is an incremental step towards #1959 that should reduce the network/IO overhead on the ATC during garbage collection.

    warning: This requires a new port to be reachable on the worker node from the web node: 7799. This communication will go away once we fully complete parallel GC, as the workers will ask the web nodes what to delete instead.

feature, breaking

  • In v3.11.0 we changed the default behavior of the git resource so that it does not fetch tags by default. In hindsight we should have been a bit more careful here, as many people depend on that behavior. We've decided to roll it back to fetching them by default, since in most cases (where tags are never deleted or re-pointed) it's not an issue to include them.

    To disable fetching of tags, configure clean_tags: true in params.

    Thanks for the PR, @mdomke!

feature

  • The ATC can now be configured with a global default build_logs_to_retain, thanks to a PR by @aeijdenberg! This is useful for operators who want more control over their database usage.

    A maximum value can also be configured to ensure users don't just set it to 9 trillion. The flags are --default-build-logs-to-retain and --max-build-logs-to-retain.

fix

  • Fixed a memory leak in the TSA introduced in v3.11.0.

feature

  • The fly set-pipeline command will no longer prompt apply configuration? if there are no changes to apply.

feature

feature

  • A fly status command has been added for checking whether or not you're logged in to the given target.

feature

  • When fly check-resource fails, it'll bubble up the error message rather than just saying error code 500.

fix

  • Work around an apparent regression/behavior change in recent versions of Chrome that prevented the pipeline UI jobs from being clickable.

fix

  • Fixed a corner case in error handling that could cause a lock to be held forever when detecting new versions of resource types. This could lead to things like builds stuck in "pending" state. Thanks to @SHyx0rmZ for the PR!

fix

  • When directed to the login page from the resource page, you will now be redirected back to where you were, rather than to the moon.

fix

  • The concourse web command is now capable of running the migration flags (--current-db-version and friends). It's still super janky (it'll run the TSA alongside your...migrations), but hey, it runs them now.

    We'll probably clean this up in the future by having the migration stuff be a separate command instead.

fix

  • fly CLI will once again helpfully instruct you to log in rather than just saying error: forbidden.

feature

  • The BOSH release now supports properties for configuring the new AWS Secrets Manager credential backend. Thanks for the PR, @x6j8x!

feature

  • When a previously-created volume disappears from a worker and the ATC tries to use it, the error message will now include the worker name and the volume handle. Thanks for the PR, @rfliam!

fix

  • The fly check-resource command will now fail more clearly when the resource's type is not found. Thanks to @jmcarp for the PR!
Assets 8