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 accessing a directory outside of the current _temp workspace directory which is created for each run.
This is not an issue on github.com as they have ephemeral runners that get destroyed or reset after each run. For GHES though the runners sometimes work for more than one job (maybe also a questionable practise) but then their disks run full because the directory from
is not wiped as its not part of the temporary workspace.
Describe the solution you'd like
I am happy/open to make a PR to refactor that logic, but I'd like to get advice first on why that architecture was chosen. Also, where would these files best belong if we make a generic PR (that does not accept the path as parameter but defaults to something inside the temporary workspace)?
Describe alternatives you've considered
Making a PR to hand in a parameter to define the working-directory from external.
Additional context
Our disks ran full that morning for 1 runner that lived quite a time and then our jobs started to fail on npm install as there was no disk space left.
The text was updated successfully, but these errors were encountered:
Checklist
Describe your proposal
actions-gh-pages/src/utils.ts
Line 22 in cc6f656
_temp
workspace directory which is created for each run.This is not an issue on github.com as they have ephemeral runners that get destroyed or reset after each run. For GHES though the runners sometimes work for more than one job (maybe also a questionable practise) but then their disks run full because the directory from
actions-gh-pages/src/utils.ts
Line 22 in cc6f656
Describe the solution you'd like
I am happy/open to make a PR to refactor that logic, but I'd like to get advice first on why that architecture was chosen. Also, where would these files best belong if we make a generic PR (that does not accept the path as parameter but defaults to something inside the temporary workspace)?
Describe alternatives you've considered
Making a PR to hand in a parameter to define the working-directory from external.
Additional context
Our disks ran full that morning for 1 runner that lived quite a time and then our jobs started to fail on
npm install
as there was no disk space left.The text was updated successfully, but these errors were encountered: