-
Notifications
You must be signed in to change notification settings - Fork 752
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
Add SBT in cache managers. #302
Conversation
Hello @fmeriaux. Could you please sync with the main branch? |
Done |
Hello @fmeriaux. Could you please add e2e tests for sbt ? |
Yes, no problem, but can you detail a little more what I have to do? |
I am so sick of receiving Github emails from Subscribers 6 a day? How can I
be attached to the thread when I unsubscribed after 5 days last year?
Please delete my email
***@***.*** ***@***.***>*
Donna Murdoch
…On Tue, 12 Apr 2022, 4:50 pm Florian Meriaux, ***@***.***> wrote:
Hello @fmeriaux <https://github.com/fmeriaux>. Could you please add e2e
tests for sbt ?
Yes, no problem, but can you detail a little more what I have to do?
I think it should be something similar to Gradle
<https://github.com/actions/setup-java/blob/main/.github/workflows/e2e-cache.yml#L18-L66>
test.
Thanks, done !
—
Reply to this email directly, view it on GitHub
<#302 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVVEBHXVXZIALDGTVVEZIOTVEUMJXANCNFSM5RQPPSSQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
According to https://github.com/coursier/cache-action#path Cache should use the default OS-dependent location. PR is updated |
The support of sbt caching has been implement recently in actions/setup-java#302 and actions/setup-java#332 by Florian Meriaux
It has just gained support via actions/setup-java#302. See also https://github.com/actions/setup-java#caching-sbt-dependencies.
It has just gained support via actions/setup-java#302. See also https://github.com/actions/setup-java#caching-sbt-dependencies. Also add type to spec in HeliosSpec.
It has just gained support via actions/setup-java#302. See also https://github.com/actions/setup-java#caching-sbt-dependencies. Also add type to spec in HeliosSpec.
https://github.com/actions/setup-java#caching-sbt-dependencies See actions/setup-java#302 - it looks like the sbt-caching functionality was informed by https://github.com/coursier/cache-action (see actions/setup-java#302 (comment) ), so setup-java may now be the 'best' solution.
https://github.com/actions/setup-java#caching-sbt-dependencies See actions/setup-java#302 - it looks like the sbt-caching functionality was informed by https://github.com/coursier/cache-action (see actions/setup-java#302 (comment) ), so setup-java may now be the 'best' solution.
…ting it's own version While working on https://github.com/guardian/gha-scala-library-release-workflow I noticed that no matter how many times I ran the workflow, `actions/setup-java` would always report `sbt cache is not found`, even if there had been no substantial change in the project - simply that `version.sbt` (the file used by https://github.com/sbt/sbt-release) had the version number in it incremented (as in guardian/play-secret-rotation@b215232). This meant that turning on `cache: sbt` would actually slow the workflow considerably, as it would never benefit from the cache being present, and would always have to save it, which could take 2-3 minutes - even though it can't take advantage of the data it's saving. As such, it would be great to exclude `version.sbt` files from the cache hash key. Background: `cache: sbt` was orginally introduced with actions#302
…ting it's own version While working on https://github.com/guardian/gha-scala-library-release-workflow I noticed that no matter how many times I ran the workflow, `actions/setup-java` would always report `sbt cache is not found`, even if there had been no substantial change in the project - simply that `version.sbt` (the file used by https://github.com/sbt/sbt-release) had the version number in it incremented (as in guardian/play-secret-rotation@b215232). This meant that turning on `cache: sbt` would actually slow the workflow considerably, as it would never benefit from the cache being present, and would always have to save it, which could take 2-3 minutes - even though it can't take advantage of the data it's saving. As such, it would be great to exclude `version.sbt` files from the cache hash key. Background: `cache: sbt` was orginally introduced with actions#302
…ting it's own version While working on https://github.com/guardian/gha-scala-library-release-workflow I noticed that no matter how many times I ran the workflow, `actions/setup-java` would always report `sbt cache is not found`, even if there had been no substantial change in the project - simply that `version.sbt` (the file used by https://github.com/sbt/sbt-release) had the version number in it incremented (as in guardian/play-secret-rotation@b215232). This meant that turning on `cache: sbt` would actually slow the workflow considerably, as it would never benefit from the cache being present, and would always have to save it, which could take 2-3 minutes - even though it can't take advantage of the data it's saving. As such, it would be great to exclude `version.sbt` files from the cache hash key. Background: `cache: sbt` was orginally introduced with actions#302
Description:
Describe your changes.
Add SBT cache manager.
Related issue:
Add link to the related issue.
#266 (comment)
Check list: