Use setup-gradle GitHub action#1092
Merged
breedx-splk merged 1 commit intoJul 25, 2025
Merged
Conversation
bidetofevil
approved these changes
Jul 24, 2025
Contributor
bidetofevil
left a comment
bidetofevil
left a comment
There was a problem hiding this comment.
LGTM. Seems faster on the initial run
breedx-splk
approved these changes
Jul 25, 2025
Contributor
breedx-splk
left a comment
breedx-splk
left a comment
There was a problem hiding this comment.
I'm excited about this -- we use it in the instrumentation builds as well. 🤞🏻
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Goal
The setup-gradle Github Action offers better build performance on CI. It caches build state such as gradle JARs and output from build tasks between jobs which therefore avoids starting the build from scratch each time. I didn't spot any alternative solution that was doing this already.
If this approach is accepted I can raise a separate changeset to do this for the other CI workflows.
Testing
Relying on the CI job. I don't have permissions to retry the job to test the cache, which may be worth doing to get an idea of the speed improvements.