Skip to content

Limit configuration cache testing to the latest version of Gradle #40794

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wilkinsona opened this issue May 16, 2024 · 0 comments
Closed

Limit configuration cache testing to the latest version of Gradle #40794

wilkinsona opened this issue May 16, 2024 · 0 comments
Assignees
Labels
type: task A general task
Milestone

Comments

@wilkinsona
Copy link
Member

wilkinsona commented May 16, 2024

For every version of Gradle in our test compatibility matrix, we test both with and without the configuration cache enabled. This doubles the number of tests for several classes for little benefit as we rarely, if ever, find bugs that are specific to the configuration cache. Given that Gradle does not enable the configuration cache by default and that it has improved significantly in the most recent versions of Gradle, we feel that it's overkill to test with it enabled as much as we do. We're going to save some resources and reduce build times by limiting our configuration cache testing to the latest version of Gradle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

No branches or pull requests

1 participant