-
Notifications
You must be signed in to change notification settings - Fork 354
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
Optimize CI a bit #1390
Optimize CI a bit #1390
Conversation
key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle.kts') }} | ||
restore-keys: | | ||
${{ runner.os }}-gradle- | ||
uses: gradle/gradle-build-action@v2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://github.com/gradle/gradle-build-action
Ref detekt/detekt#3723, it's really so fast to run jobs, and many other advantages.
|
Looks like the |
I've tested again on my repo, it passed. See Goooler#1 |
uses: actions/cache@v1 | ||
with: | ||
path: ~/.gradle/caches | ||
key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle.kts') }} | ||
restore-keys: | | ||
${{ runner.os }}-gradle- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
gradle/gradle-build-action
just caches the .gradle
folder, .m2
folder is handled by actions/cache.
### 📝 Description Use gradle-build-action to speed up build on CI and bump all action versions. ### 🔗 Related Issues
📝 Description
Mainly for using gradle-build-action to speed up build on CI, and bump action versions by the way.
🔗 Related Issues