Closed charlesluzar closed 1 year ago
The action just checks if the cache-path
exists on self-hosted runners. If it does it just updates the environment.
A better use for self-hosted is to add the cache-path: ${{ runner.tool_cache }}/flutter/${{ env.FLUTTER_VERSION }}-${{ env.FLUTTER_CHANNEL }}
parameter. This way you can have multiple versions installed in parallel. Make sure to clean the _tools/flutter
folder beforehand.
@subosito Not sure, maybe the action can catch the different local version and then delete/re-install?
@kuhnroyal That did the trick. Seems a helpful thing to add to the README for people running on self-hosted runners. Happy to submit a PR if requested, just let me know. I'll leave it to an existing contributor to close the issue if desired. Thanks so much!
I'm trying to get this action to install Flutter@3.0.5 but it won't seem to install anything higher than 3.0.1 on a
macos
VM running theself-hosted
actions runner.Things I tried:
architecture
with and without quotesx64
andarm64
architecturesflutter-version
withoutchannel
and vice-versasubosito/flutter-action@v1
Nothing I tried got anything higher than 3.0.1 to install.
Here's a script I used to test on a
macos
machine:Here is the output. (If you'd like the raw logs just let me know, I figured this is easier to look at.)