Release History
|
You can find previous versions of the Develocity Build Cache node documentation in our legacy documentation archive |
Previous Versions
21.1
-
[FIX] Storing a cache entry can fail if an earlier eviction of that entry encountered an error
21.0
-
[NEW] Compatibility with Develocity application internal operational metric-gathering solution
20.2
-
[NEW] Set a socket timeout on connections opened by Develocity for replication
-
[NEW] Removed support for optimized HTTPS on the "Linux aarch_64" platform
20.1
-
[FIX] After a high number of evictions, some cache entries may be removed from the cache too early.
-
[FIX] Eviction fails to trigger under sustained high load.
20.0
-
[NEW] Revised permission model that applies to all projects (when connected to Develocity with project-level access control enabled)
-
[FIX] Logging of access token signing key retrieval is noisy (when connected to Develocity)
19.1
-
[NEW] Improved cache eviction efficiency
-
[FIX] Resource leak at startup when namespaced cache entries are present
19.0
-
[NEW] Support for short-lived access tokens (when connected to Develocity)
-
[NEW] Build Cache node JAR is compiled for and requires Java 21
-
[FIX] Bazel builds may cause shutdown when Build Cache node uses slower disks
18.1
-
[FIX] Cache entry eviction may fail to finish and cause 'out of disk' errors
17.1
-
[NEW] System property to toggle cache event publication (when connected to Develocity)
-
[NEW] Capture AWS ELB trace identifier (X-Amzn-Trace-Id) header value
17.0
-
[NEW] Project-level access control support (when connected to Develocity)
-
[FIX] Warnings caused by presence of IP addresses with ports in X-Forwarded-For HTTP header
-
[FIX] Misleading warning that Build Cache is effectively inaccessible when registered with Develocity
16.1
-
[FIX] Idle HTTP client connections can cause cache entries to become inaccessible
16.0
-
[NEW] Build Cache node can be used as a remote store for Bazel builds (when connected to Develocity)
15.1
-
[FIX] Idle HTTP client connections can cause cache entries to become inaccessible
15.0
-
[NEW] Build Cache node JAR is compiled for and requires Java 17
-
[NEW] Official Docker image includes JDK 17 instead of JDK 11
-
[NEW] Cache entries are managed more efficiently
-
[FIX] Replication of entries when available space is low can cause Build Cache node to run out of space
-
[FIX] Too-large cache writes are rejected