Concourse v5.4.0 Release Notes
Release Date: 2019-07-19 // over 4 years ago-
known Issues
๐ > We've observed a memory leak with this release. Please avoid upgrading to this release if you are using a multi-tenant concourse with heavy load. You can follow along with our investigation in #4150.
๐ง >
fly
may segfault on execution when running on certain versions of Linux. Workaround steps can be found here: #4141 (comment)๐ฑ ๐ feature, breaking
- We have switched to a more efficient algorithm for streaming volumes between various components of the system - the
web
andworker
nodes now transmit volumes compressed with the Zstandard algorithm rather thanGzip
-fly
is affected, too (when uploading/downloading artifacts duringfly execute
). We're hoping this will resolve some general complaints of steps being slow to start or appearing to "hang" in clustered environments. note: this will require upgrading your workers #3880.
๐ฑ ๐ feature
- ๐ Because of the efficiency gained from employing Zstandard compression to volume streaming, the CPU on the web and worker nodes is no longer a limiting factor. Now volumes will be streamed over multiple parallel connections, and we have seen some very exciting improvements in the time taken to initialize build steps. You can see some of our measurements in the discussion on this issue #3993.
๐ฑ ๐ feature, breaking
- ๐ On the build page all steps are now collapsed by default. This means that the build page loads faster, but if you want to watch the logs in real time, you will need to click on the header of the running step #4058.
๐ฑ ๐ feature
- Improved the appearance of the sidebar (re-introduced in v5.2.0) in response to user feedback. Teams and pipelines are now easier to distinguish, and there are nicely styled tooltips for long items #4032.
๐ฑ ๐ feature
- โก๏ธ @maryamklabib optimized the
pool
resource -check
andin
scripts will run faster by using shallow cloning concourse/pool-resource#49.
๐ฑ ๐ feature
- ๐ When you manually trigger a build through the web UI, the 'prep' section at the top of the build page now shows a spinner on the entries marked "discovering new versions of..." while the resource checks are in progress. As the checks resolve, the spinners will become checkmarks, so you'll have a better sense of what might be holding up your build #3970.
๐ฑ ๐ feature
- @deadNightTiger added a
fly completion
subcommand that allowsfly
to output autocompletion for thebash
andzsh
shells #4012.
๐ฑ ๐ feature
- โฑ When you abort a pending build before it gets scheduled, the build page will now report it as 'cancelled' instead of showing a loading spinner forever #3922.
๐ฑ ๐ feature
- โก๏ธ The CSS optimizer used in building the web UI has been upgraded, so the resulting CSS is slightly smaller, which should result in some faster page loads #4004.
๐ฑ ๐ fix
- ๐ง @cappyzawa fixed an issue where the
s3
resource would break whendisable_multipart: true
was set in the source configuration, and a tracked file was smaller than the minimum upload part size for the configured s3-compatible blobstore concourse/s3-resource#131.
๐ฑ ๐ fix
- ๐ @robwhitby fixed an issue where re-checking a resource would cause the metadata from its latest version to be erased #4028.
๐ฑ ๐ fix
- ๐จ @cappyzawa fixed up
fly
to behave like a sensible Unix tool when passing the-h
or--help
flag: it now prints the usage text onstdout
and returns a successful status code #4064.
๐ฑ ๐ fix
- ๐ @cappyzawa fixed a small issue where the
-j
or--json
flag was not honored when runningfly get-team
#4046.
๐ฑ ๐ fix
- ๐ Fixed a regression found recently involving momentum based scrolling on build pages on iOS browsers The fix was also applied to the sidebar and the dashboard #4050
๐ฑ ๐ fix
- ๐ The BOSH Backup and Restore job for the database now works properly if you provide your database configuration via a BOSH link. Before, it would always use a hardcoded default if you didn't explicitly specify, causing BOSH links to be ignored concourse/concourse-bosh-release#41.
๐ฑ ๐ fix
- ๐ Fixed a bug where, if your local machine is running Mac or Linux and you run
fly execute
with--input
against a cluster with a mix of Linux and Windows workers, your files could get uploaded to a Windows worker, where ther permission metadata would be stripped off. Nowfly execute
makes sure only to upload user artifacts to workers matching theplatform
of the task being executed #4066.
- We have switched to a more efficient algorithm for streaming volumes between various components of the system - the