v5.0.0

Replace Nexus cache with generic remote HTTP cache implementation.

Notable breaking changes:

• The plugin was renamed from "plugin-scripts-cache-nexus" to "plugin-scripts-cache-remote". This also resulted in all corresponding configuration options and environment variables to be renamed accordingly.
• The "Host" and "Repository" configuration options where replaced by a more generic "Url" option.
• The username and password (if provided) will also be used for downloading artifacts, instead of just for uploading them.

Check the caches documentation (README.md) for details.

v4.9.0

Introduce statistics service to collect information about cache usage.

v4.8.1

Fix a bug where the file cache cleanup would crash if multiple processes try to perform cleanup at the same time, e.g. in a monorepo with multiple workspaces.

v4.8.0

New configuration option to ignore concurrent modifications. Normally, the plugin will detect when source files are modified while a script is being executed. In this case, the cache will not be filled, because of the uncertainty which state was being used. This should usually avoid bugs, where a cache entry is created with an unmatched cache key. But for certain scripts (e.g. formatting where output is empty) it might be intended to cache anyway. This option allows to do that.

v4.7.0

Add new config option to ignore script execution results in dependent workspaces

v4.6.0

Detect concurrent modification of cached files

The plugin is now able to detect concurrent modification of the cached files while a script is being executed. This can happen when a script is being started, takes a while to run, and while it is doing so, the developer continues to modify source files. This results in uncertainty about which state of the files the script was executed on. To avoid faulty cache entries, the cache will not be updated in this case.

v4.5.0

Updated package manager and 3rd party dependencies.

v4.4.0

Add new config option to fine-tune whether changes in workspace dependencies are relevant for caching.

v4.3.0

Support for JSON5 features like comments and trailing commas in configuration files.

v4.2.0

Cache entries restored from slower (higher order) caches are now saved in faster (lower order) caches. For example if you have two caches, a shared remote cache and a local file cache, then a result being restored from the slower remote cache will be saved to the local file cache making future cache hits even faster.