Replies: 3 comments 6 replies
-
what would you clean after each build? also, 6*50mb would be 300mb... far away from 14gb... are you sure there isn't something else going on? that said, if the problem is temp files, maybe use a reduced |
Beta Was this translation helpful? Give feedback.
-
I submitted a PR that may help a small bit by having |
Beta Was this translation helpful? Give feedback.
-
Oh wait - maybe it is something in goreleaser? I was just testing the size differences in metio/terraform-provider-k8s#137 (thanks @jftuga) and realized that I only looked at the size of the compiled binary before but not the .zip file that is created at the end. Zipping that ~700MB file produces a ~46MB file. So I guess what I'm asking is: Can I somehow tell goreleaser to produce a .zip per OS/ARCH before continuing with another build target and clean up inbetween those builds? |
Beta Was this translation helpful? Give feedback.
-
Hi folks,
I'm currently running into a 'no space left on device' error while trying to release one of my projects (latest run). The final release artifacts are around 50MB and I build for 6 different platforms. Since GitHub runners have 14GB of disk space, this should fit nicely, however this disk space is used for tooling as well as some compile artifacts produces by the Go compiler which eats up all the available space. My guess is that the compile artifacts take up the majority of disk space since the project is huge (millions of lines of code).
Is there any way to call something like
--clean
after each compiled binary, so that I have a higher chance of succeeding with a build?Thanks!
Beta Was this translation helpful? Give feedback.
All reactions