- The Netherlands
- https://melroy.org
- Joined on
2023-07-14
I think this is a Forgejo UX problem rather than a runner problem. And I also find that unexpected and inconvenient.
Ps. could still…
That being said. I think hashFiles can hopefully be fixed in the future.
Yup that works:
For others that might need this:
- name: Calculate yarn.lock hash
id: yarn-lock-hash
…Ow.. I see. But then again, Docker shouldn't be aware of the host location on disk. RIght? So the hashFiles expression should become Docker aware somehow and search the file within the check-out…
silently succeeds and displays nothing. But in the log it always fails with
Unable to filepath.Walk: lstat /workspace/.... You are correct, it does not look where it should. The evaluation…
I think you're on the right track but that's unexpected: I would assume the evaluation happens with a current working directory that is the workspace. Is
**/yarn.locksupposed to match…
Ow I see.. by default your checkout location (part of checkout action) is not /workspace I think.. But something like /home/codeberg-runner/.cache, right.
But the cache action expects that…
This is a problem in hashFiles() I presume?
Running action on PR: https://codeberg.org/Kbin/kbin-core/pulls/755
Full runner log:
Jul 14 21:39:26 ubuntu-server forgejo-runner[1852327]: time="2023-07-14T21:39:26+02:00" level=info…