Closed melund closed 12 months ago
You can try setting pixi-bin-path: ${{ runner.temp }}\Scripts\pixi.exe
as described in the self-hosted runner section of the readme.
I'm not really a fan of checking the version since this will lead to more logic that needs to be maintained. Maybe just deleting the other file if it exists would be the best way...
Setup-pixi often falls into a non-working state on my self-hosted workers. I happens if it somehow doesn't managed to clean up after itself nicely (
post-cleanup: true
).Then on next run the pipeline fails with:
Maybe just force delete it, or check if the version of pixi is OK, and then just continue.
Right now I have a workaround steps in the pipeline to recover from this. Any other good ideas?