[Gradle] Add buildkite ci validation script for configuration cache #110269
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
breskeby
added
>non-issue
:Delivery/Build
|
Pinging @elastic/es-delivery (Team:Delivery) |
breskeby
force-pushed
the
add-configuration-cache-evaluation-script
branch
from
f069d73
to
25e6f20
Compare
breskeby
force-pushed
the
add-configuration-cache-evaluation-script
branch
2 times, most recently
from
e4edae6
to
5f5f42e
Compare
breskeby
force-pushed
the
add-configuration-cache-evaluation-script
branch
from
5f5f42e
to
9a4a753
Compare
breskeby
added
the
auto-merge-without-approval
rjernst
pushed a commit
to rjernst/elasticsearch
that referenced
this pull request
Aug 7, 2024
…lastic#110269) We see gradle cache incompatibilities sneaking into our code base. Until we can enable this feature by default we should regular run checks existing configuration cache achievements are not degrading. This change includes: - updating spotless gradle plugin to configuration cache compatible version (its still BETA but imo good enough for our needs)
mhl-b
pushed a commit
that referenced
this pull request
Aug 8, 2024
…110269) We see gradle cache incompatibilities sneaking into our code base. Until we can enable this feature by default we should regular run checks existing configuration cache achievements are not degrading. This change includes: - updating spotless gradle plugin to configuration cache compatible version (its still BETA but imo good enough for our needs)
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this pull request
Sep 4, 2024
…lastic#110269) We see gradle cache incompatibilities sneaking into our code base. Until we can enable this feature by default we should regular run checks existing configuration cache achievements are not degrading. This change includes: - updating spotless gradle plugin to configuration cache compatible version (its still BETA but imo good enough for our needs)
davidkyle
pushed a commit
to davidkyle/elasticsearch
that referenced
this pull request
Sep 5, 2024
…lastic#110269) We see gradle cache incompatibilities sneaking into our code base. Until we can enable this feature by default we should regular run checks existing configuration cache achievements are not degrading. This change includes: - updating spotless gradle plugin to configuration cache compatible version (its still BETA but imo good enough for our needs)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We see gradle cache incompatibilities sneaking into our code base. Until we can enable this feature by default
we should regular run checks existing configuration cache achievements are not degrading.
This change includes: