gradle / gradle/develocity-build-validation-scripts
Consider configuring `failIfNotFullyCacheable` to `true` by default in the composite workflows
Open
- Dominant language
- Shell
- Stars
- 115
- Forks
- 23
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 6
Description
`failIfNotFullyCacheable: true` should be the default behavior and `failIfNotFullyCacheable: false` should be the exception.
If a user forgets to configure `failIfNotFullyCacheable: true` they will have a false sense of security thinking their build is optimized when it may not be.
This would be a breaking change, but only if `failIfNotFullyCacheable` is not already configured _and_ the user's build has cache misses. It's reasonable to assume those cases are a misconfiguration.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.