You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
You might be able to speed up your workflow runs by using the caching features that come with the latest versions of actions/setup-node and actions/setup-java.
Describe the solution you'd like
With the new actions, enabling caching is very easy, you don't need to figure out any caching keys or do other complicated things. You only need to add a few lines to the workflow files.
Make sure the version of the action you're using supports the cache feature. 😉 I think you need to update your version of setup-java first to be able to use caching.
Thanks @HonkingGoose , we'll see what we can do here. We can definitely make use of both in different ways and get rid of a lot of our current manually caching configurations.
Is your feature request related to a problem? Please describe.
You might be able to speed up your workflow runs by using the caching features that come with the latest versions of
actions/setup-node
andactions/setup-java
.Describe the solution you'd like
With the new actions, enabling caching is very easy, you don't need to figure out any caching keys or do other complicated things. You only need to add a few lines to the workflow files.
Make sure the version of the action you're using supports the cache feature. 😉 I think you need to update your version of
setup-java
first to be able to use caching.Official documentation:
setup-node
readme, caching packages dependenciessetup-java
readme, caching packages dependenciesDescribe alternatives you've considered
Keep things as they are.
Additional context
I suggested this in a PR that we've now closed: #3386 (comment)
The text was updated successfully, but these errors were encountered: