-
Notifications
You must be signed in to change notification settings - Fork 17
Caching doesn't work (for me) #1
Comments
Thanks for spotting that out. Will try to resolve asap |
Could you change your workflow file? - name: Prepare GraalVM
uses: DeLaGuardo/[email protected]
with:
graalvm-version: "19.3.0.java8"
- name: Second prepare GraalVM
uses: DeLaGuardo/[email protected]
with:
graalvm-version: "19.3.0.java8"
- name: Install native-image
run: |
echo
gu install native-image
|
I'm still waiting for the new job to complete Also I didn't mention it, but this is a run on a mac ( |
Ok the step I've been able to cache other steps (maven dependencies), but for this I had to add:
I couldn't find anything like that in your code (could have looked wrong of course) |
That is correct. I'm doing almost the same in my company's project. The only difference - you do not need |
I think you are correct that it doesn't make a big difference, |
So I guess this issue can be closed, isn't it? |
I was talking about the maven caching, not the GraalVM download. That is still not cached. Do you mean I should add an |
I tried to add "caching between jobs" via |
Hi Kirill,
Thank you for sharing this Github Action!
It works perfectly except for caching of the GraalVM download. It seems to add 30 unnecessary seconds for each build.
This is my configuration:
The
Prepare GraalVM
step takes around 30 seconds. Did I miss something in my configuration?It seems your code tries to detect this situation here https://github.com/DeLaGuardo/setup-graalvm/blob/master/src/installer.ts#L43
The text was updated successfully, but these errors were encountered: