github concourse/concourse v7.9.0

latest releases: v7.11.2, v7.11.1, v7.11.0...
18 months ago

🚨 Breaking

  • Fix DB out of range error due to build numbers exceed the integer limit (#8390) @xtremerui πŸ”—

    • To allow the migration to run Postgresql version has to be v11+. It happens to be a good timing to drop support of Postgresql v9.6.
  • Fixed a bug of leaking resource cofig scope ids. (#8620) @evanchaoli πŸ”—

    • When global-resources is enabled, resource_config_scopes tables leaked IDs. A side effect of the bug is that unnecessary insert will be performed (see #8618 for details). So, this PR will fix the ID leaking problem and improve performance also.
    • When global-resources is enabled, old resources weren't affected. This fix ensures old resources to switch to global scopes.

    BREAKING: With this change, when switching global-resources from OFF to ON, all resource histories will be lost. It is equivalent to changing source of a resource and causing version history to be lost. Depending on a resource's check behavior, versions may be regenerated.

    If your deployment has turned ON global-resources before the upgrade, or you choose to stay with global-resources OFF, this "breaking" change won't impact your deployment.

    If you upgrade to this version then turn ON global-resources, as described, version histories will lost. You can turn OFF global-resources again and old version histories should come back.

    Note that, if your cluster has turned ON global-resources, and you plan to turn it OFF, no matter what version it is, after turning OFF global-resources, each resource will have an unique version history, thus shared version history will be lost. The behaviour comes with global-resources and it has nothing to do with this change.

✈️ Features

  • Bump dependencies for worker runtime to support Ubuntu Jammy Jellyfish

    • Noted, guardian runtime is still under development to fully support Ubuntu Jammy. In fact, it does not work on any linux distribution with cgroups v2 enabled. We decided to bump the dependencies still for users who want to use latest linux distribution and willing to tweak their OS to enable cgroups v1.
  • load_var step supported var interpolation for file and format (#8387) @evanchaoli πŸ”—

  • Enhancement of component scheduling so that workloads are distributed across ATCs more evenly (#8463) @evanchaoli πŸ”—

  • Turn off connection tracker by default and provide an option to turn on. (#8480) @evanchaoli πŸ”—

    • Disable /debug/connections at ATC start time. It can be enabled at runtime by /debug/connections/on or be disabled by /debug/connections/off again.
  • Enhance Vault API client to auto retry upon rate limit. (#8481) @evanchaoli πŸ”—

    • Enhanced Vault credential manager to auto retry when hitting Vault rate limit error. Vault started to support rate limit since 1.5. When setting rate limit on Vault, it's better to enable rate limit HTTP response header by vault write sys/quotas/config enable_rate_limit_response_headers=true, so that the response header Retry-After may guide the Vault API client to retry after a reasonable duration.
  • Remove "check build started" and "check build finished" metrics (#8485) @evanchaoli πŸ”—

    • To monitor checks, use "check started" and "check finished" instead.
  • Support a way to skip implied get after put. (#8492) @evanchaoli πŸ”—

    • Added no_get option to put step to skip implied get. For example:
      - put: email
        no_get: true
        params:
          ...
  • Add --check-container-placement-strategy. (#8494) @evanchaoli πŸ”—

  • Explicit error messeges in p2p streaming (#8559) @dhantha πŸ”—

  • New pipelines without build should be paused automatically with a configurable interval. (#8577) @SimonXming πŸ”—

    • Using params pause-pipelines-after, so pipelines could be paused automatically with configurable interval.
  • Stream: Adding new NextEventRaw method (#8588) @gaelL πŸ”—

  • Change id of table resource_config_scopes to bigint (#8606) @evanchaoli πŸ”—
    Convert id column of the resource_config_scopes table and all tables referencing resource_config_scope_id to a bigint.

  • Performance optimize on accessor. (#8613) @evanchaoli πŸ”—
    Optimized performance of the login authentication process, which will benefit large deployments that has a lot teams and a lot of UI/fly accesses.

🐞 Bug Fixes

  • Since v7.4.0, the Concourse linux tarball in attached binaries has been using the ubuntu version with size 1GB+. Refer to this CI fix for details. Now the linux tarball is set to the version with alpine based resource types again.

  • Add tooltip to username if overflow (#8341) @xtremerui πŸ”—

    • When username is overflowing, show a hovering tooltip with full name in web UI so it won't block buttons below it e.g. trigger build buttons in build page.
  • Fix step header key value UI in build page (#8406) @xtremerui πŸ”—

    • Fix line height of step header in build page when there is sub header like instance vars or across
  • Fixed a bug of error invalidated-worker-resource-cache-exists (#8416) @evanchaoli πŸ”—

  • Add missing lock metrics ResourceGet and VolumeStreaming. (#8468) @evanchaoli πŸ”—

  • Check build should not auto retry. (#8493) @evanchaoli πŸ”—

    • If a check happens to drop into endless retry, there is no way to abort a check build.
  • Fix a bad SQL for check gc. (#8500) @evanchaoli πŸ”—

    • Optimized performance of check-build-events collector.
  • Use pq.Array to avoid hitting parameter limits (#8528) @ae-govau πŸ”—

  • Change host to event_host tag for Datadog integration (#8544) @pablokbs πŸ”—

  • Fix bug in testflight suite env var assignment (#8594) @elliot-gould πŸ”—

    • Now it should allow users to use environment variables to override local user credentials properly.
  • Fix across step states bug (#8634) @xtremerui πŸ”—

    • Fix a bug where sub step of across step showing incorrect state.

🀷 Miscellaneous

πŸ“¦ Bundled resource types

Don't miss a new concourse release

NewReleases is sending notifications on new releases.