- Notifications
You must be signed in to change notification settings - Fork165
Classic disk space rewrite#531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Rewrote set min disk space
cf-ci-bot commentedDec 26, 2022
[CI] Staging environment is athttp://staging-docs.codefresh.io.s3-website.us-east-1.amazonaws.com/classic-disk-space-rewrite/docs/ |
| Because a portion of the disk space is already utilized by cache, a build can run out of disk space and fail with the 'no space left on device' error. | ||
| Codefresh calculates the available range according tothe disk size, and automatically sets the disk space for the build volume to 70% ofthetotal disk space. You can either retain thedefault allocation or change as needed. | ||
| To prevent out-of-space scenarios that lead tofailed builds, you can set theminimumdisk spaceyou needfor thepipeline'sbuild volume. Defining the minimum disk space ensures that Codefresh allocatesthedesignated disk space at the start of thespecific build without cached data. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Its not correct that youll start without cache at all.
This is only true in case a new freah disk will be chosen. And this will only happen if eitger all disks are in use and thus no previous one is free or due to no existing disk with enough space left
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Thank you Itai
No description provided.