There is a new experimental method of resource checking, which is off by default but can be turned on via
The entire system has been redesigned to be asynchronous, but that shouldn't have any affect on your existing workflows.
fly check-resource-typewill continue to work the way you expect them to (except for a small change to the command output). In addition you can now specify an
--asyncflag if you don't want to wait for the check to finish.
It's worth noting that concourse performs a lot of checks (like A LOT). Since we're now storing checks in the database, this table will tend to grow very quickly. By default checks get gc'ed every 6 hrs, but this interval can be configured by specifying a
CONCOURSE_GC_CHECK_RECYCLE_PERIOD. If you want to reduce the number of checks that happen, you can start making heavier use of the
webhookendpoint to trigger checks from external sources. This allows you to significantly reduce the
check_everyinterval (default 1m) for your resource without impacting the time it takes to schedule a build.
- Fly has a new sub-command
pin-resource, which will pin a resource (and optionally comment) given at least one field of the version to pin to #2702 #4417.
- When configuring a job, a subset of the pinned version's fields can now be provided to the
version:field on a
This feature is currently opt-in. To learn how to enable it, check out the docs.
- @ralekseenkov added a web runtime flag
CONCOURSE_SECRET_CACHE_DURATION_NOTFOUNDto set a separate caching interval when a secret is not successfully found in the config store. Defaults to 10s. Addresses #3895 #4009.
- The cluster name can now be added to each and every log line with the handy dandy
--log-cluster-nameflag, available on the
webnodes. This can be used in a scenario where you have multiple Concourse clusters forwarding logs to a common sink and have no other way of categorizing the logs. Thanks again @evanchaoli! #4387
- @thoHeinze added
CONCOURSE_GARDEN_NETWORK_POOLas configurable flag in BOSH release.
Defaults to Garden's range of 10.254.0.0/22. Addresses #4153.
- @joshzarrabi and @aemengo added
CONCOURSE_GARDEN_MAX_CONTAINERSas configurable flag in BOSH release.
Defaults to 250. Please note that setting this limit over 250 has not been tested by the Garden team or the Concourse team. #43.
- When the web node is instructing a worker to create a container, any logs emitted will mention that worker's name #4438. Thanks @christophermancini!
- @SimonXming added the
content_trust:field to the
registry-image resource, so now you can sign your container images with a notary server concourse/registry-image-resource#41, concourse/registry-image-resource#46.
- @robwhitby fixed an issue with
fly loginwhere Safari would block your token from being transferred to fly #4314, #4423, #4439.
flynow validates that, when specifying a specific
getstep, only string values (no nested YAML) are allowed #4236.
- The fly
set-teamdocumentation when running
--helppreviously suggested that a list is a valid input to any auth configuration flags. This doesn't mean you can supply a comma-separated list to the flag, rather that the flag can be provided multiple times. The fly
set-teamhelp documentation now reflects this, thanks to @niall-byrne! #4348
- @nelsam fixed a delicate bug where
/opt/resource/outscripts in resources could crash web nodes by outputing
stdout, causing a nil pointer dereference #4442.
- @kmdouglass fixed a bug introduced by #3037 in v5.5.0 where prometheus metrics would get clogged up with data about workers that were no longer registering #4445.
- @bodin fixed an issue with the
semver-resourcewith the git driver: now the resource will create the
file:specified in the source configuration if it doesn't already exist exist concourse/semver-resource#102.
- @mgsolid fixed an issue the git driver for the
semver-resourcewould go into an infinite loop when
git pushfailed concourse/semver-resource#92.
- @CliffHoogervorst fixed an issue where the [
git resource] would show too many commits when
paths:was specified concourse/git-resource#271.