Concourse v5.5.0 Release Notes

Release Date: 2019-09-06 // over 4 years ago
  • ๐Ÿฑ ๐Ÿ”— feature

    • ๐Ÿ‘ท There is a new container placement strategy, limit-active-tasks. If you specify this strategy, the cluster will maintain a counter of the number of task containers currently running on each worker. Whenever it is time to run a new container, when this strategy is in use, the worker with the fewest active tasks containers will be chosen to run it.
      โฑ There is also an optional 'max active tasks per worker' configuration. If this is set to a positive integer, you will see the following behaviour: If all workers are at their active task limit, you will see the message All workers are busy at the moment, please stand-by. and the scheduler will re-try a minute later. This pattern will repeat each minute indefinitely, until a worker is available.
      Thanks to @aledeganopix4d for all their hard work on this feature! #4118, #4148, #4208, #4277, #4142, #4221, #4293, #4161, #4315

    ๐Ÿฑ ๐Ÿ”— feature

    • ๐Ÿš€ We have changed our release notes flow! Now, contributors can add draft release notes right in their PRs, by modifying the release-notes/latest.md file in the concourse/concourse repo #4312.

    ๐Ÿฑ ๐Ÿ”— feature

    • ๐Ÿ— In the past, admins (owners of the main team) had permission to modify the auth configuration for other teams in the same cluster. Now, admins also have full control over pipelines, jobs, resources, builds, etc for all teams. Using fly, they can log in to any team on the cluster as though they are an owner #4238, #4273.

    ๐Ÿฑ ๐Ÿ”— feature

    • ๐Ÿ— We noticed after #4058 (where build steps are collapsed by default) that it wasn't very easy to see failing steps.
      Now a failing step has a red border around its header, an erroring step has an orange border, and a running step has a yellow border. #4164, #4250

    ๐Ÿฑ ๐Ÿ”— feature

    • ๐Ÿ”ง On particularly busy clusters, users have observed metrics events being dropped due to a full queue #3937. @rudolfv added a configurable buffer size for metrics emission, regardless of your configured emitter. This should allow operators to trade memory pressure on the web nodes for reliability of metric transmission.

    ๐Ÿฑ ๐Ÿ”— feature

    • ๐Ÿ”ง @rudolfv also added some features for the special case of InfluxDB metrics. To decrease the request load on InfluxDB, you can configure the number of events to batch into a single InfluxDB request, or you can specify a hardcoded interval at which to emit events, regardless of how many have accumulated #3937.

    ๐Ÿฑ ๐Ÿ”— feature

    • @nazrhom improved the output of fly targets to show an error message in the table if your token for a given target is invalid #4181, #4228.

    ๐Ÿฑ ๐Ÿ”— feature

    • 0๏ธโƒฃ Concourse admins can now run fly active-users and get a summary of all the users on the cluster, filtering by their last login time (the last 2 months by default) #4096.

    ๐Ÿฑ ๐Ÿ”— feature

    ๐Ÿฑ ๐Ÿ”— feature, breaking

    • ๐Ÿ— Now requests from the web nodes to the garden servers inside workers (i.e. when creating containers) will time out after 5 minutes. This means that if you have a lot of latency or your garden servers are slow, your builds and/or resource checks will start to fail. In general, we have found that failing earlier in cases like this is preferable to hanging forever or failing silently #4137.

    ๐Ÿฑ ๐Ÿ”— feature

    • ๐Ÿ”ง Fly has the ability to autocomplete certain configurations for certain shells. @cappyzawa added some more, allowing team and worker names to be autocompleted in fly commands #4087.

    ๐Ÿฑ ๐Ÿ”— feature

    ๐Ÿฑ ๐Ÿ”— feature

    • @mgsolid added a pre_without_version param to the get and put steps associated to the semver resource. This allows for notating pre-releases without an associated "RC number" (like the -SNAPSHOT suffix often seen on pre-release builds managed by Maven) concourse/semver-resource#94.

    ๐Ÿฑ ๐Ÿ”— feature

    ๐Ÿฑ ๐Ÿ”— feature

    ๐Ÿฑ ๐Ÿ”— feature

    • ๐Ÿš€ The number of assets listed per release was raised by @oppegard from 30 to 100 on the Github release resource. This will hopefully prevent most issues where the resource would not have the full list of assets to download concourse/github-release-resource#85.

    ๐Ÿฑ ๐Ÿ”— feature

    ๐Ÿฑ ๐Ÿ”— feature

    ๐Ÿฑ ๐Ÿ”— feature

    • ๐Ÿ— Build step headers are now sticky, staying at the top of the body on the build page instead of scrolling out of sight as you navigate long logs. This should make it easier to keep track of which step you're inspecting in complicated jobs. #4230

    ๐Ÿฑ ๐Ÿ”— fix

    • When using the overlay volume driver, you would have to be cautious about preserving your mount table. If it had been cleared, you're volumes would appear empty. Baggageclaim now has the capability to recover missing mounts when the process restarts. #4264

    ๐Ÿฑ ๐Ÿ”— fix

    • @evanchaoli improved fly - when outputting sample commands to the terminal, the CLI is aware of the path from which it is being executed #4284.

    ๐Ÿฑ ๐Ÿ”— fix

    • ๐Ÿ’ป The web UI used to silently break when your token (which includes a potentially-long JSON-encoded string detailing all the teams you are part of and what roles you have on them) was longer than the size of a single cookie (4096 bytes on most browsers!). This limit has been increased 15-fold, which should unblock most users on clusters with a lot of teams #4280.

    ๐Ÿฑ ๐Ÿ”— fix

    • ๐Ÿš€ For the past few releases, the web nodes have allowed themselves to make up to 64 parallel connections to the database, to allow for parallelizing work like GC and scheduling within a single node. @ebilling has configured the web node's tolerance for idle connections to be more lenient: If a node has been using more than 32 of its available connections, up to 32 connections will be allowed to stay idly open. Anecdotally, CPU savings (resulting from less opening/closing of connections) of up to 30% have been observed on web nodes because of this change. Furthermore, the total max connection pool size has been made configurable - this should allow operators to avoid overloading the max connection limit on the database side #4232.

    ๐Ÿฑ ๐Ÿ”— fix

    • ๐Ÿ›  @josecv found and fixed a subtle bug where, if you had a try step and you aborted while the hooked step was running, your whole web node would crash! Good catch #4252.

    ๐Ÿฑ ๐Ÿ”— fix

    • ๐Ÿ @aledeganopix4d fixed an issue where the logs for a Windows or Darwin worker get populated with irrelevant error messages #4167.

    ๐Ÿฑ ๐Ÿ”— fix

    ๐Ÿฑ ๐Ÿ”— fix

    • ๐Ÿš€ Since the pipeline-operator role was introduced in v5.2.0, the tag that appears on the dashboard pages has been improperly formatted. Thanks to @paroxp for noticing and fixing this #4170.

    ๐Ÿฑ ๐Ÿ”— fix

    ๐Ÿฑ ๐Ÿ”— fix

    • The get-team command for fly will now take team-name as an argument for the team name instead of just team. Thanks to @cappyzawa for finding this inconsistency! #4086

    ๐Ÿฑ ๐Ÿ”— fix

    • ๐Ÿ›  @xavierzwirtz also fixed hg.pull by passing the sourceUri in the Mercurial resource. This could fix some issues where Mercurial wasn't saving the full uri in the hgrc file concourse/hg-resource#13.

    ๐Ÿฑ ๐Ÿ”— fix

    • 0๏ธโƒฃ Scrollbars have been given a touch of the Concourse design language. It should no longer use browser defaults. #4355

    ๐Ÿฑ ๐Ÿ”— fix

    • ๐Ÿ›  Fixed a (probably-long-standing) issue where the pipelines in the sidebar could randomly rearrange #4375.