diff options
| author | Jürg Billeter <j@bitron.ch> | 2019-03-06 15:14:13 +0100 |
|---|---|---|
| committer | Jürg Billeter <j@bitron.ch> | 2019-03-16 07:24:58 +0100 |
| commit | 3951eb56ceb810bc1279927efd836c833759823a (patch) | |
| tree | e5a25a0508d3d08247786d386db010179788938e /NEWS | |
| parent | 169acc1afc700d3fe050769c81e8c01af489e9df (diff) | |
| download | buildstream-3951eb56ceb810bc1279927efd836c833759823a.tar.gz | |
Rename cache-buildtrees option value 'failure' to 'auto'
We anticipate other cases than build failures where buildtree caching
will be required. E.g., incremental workspace build with remote
execution. Or running tests in a buildtree in parallel with the build of
reverse dependencies.
This renames the option value 'failure' to the more generic 'auto' to
cover these other cases as well.
Diffstat (limited to 'NEWS')
| -rw-r--r-- | NEWS | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -137,7 +137,7 @@ buildstream 1.3.1 Element types without a build-root were already cached with an empty build tree directory, this can now be extended to all or successful artifacts to save on cache overheads. The cli main option '--cache-buildtrees' or the user configuration cache - group option 'cache-buildtrees' can be set as 'always', 'failure' or 'never', with + group option 'cache-buildtrees' can be set as 'always', 'auto' or 'never', with the default being always. Note, as the cache-key for the artifact is independant of the cached build tree input it will remain unaltered, however the availbility of the build tree content may differ. |