-
-
Notifications
You must be signed in to change notification settings - Fork 6
Trino rebuild broke the Docker build #722
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
So just compiling Trino itself seems to use around 10-12GB of space (sorry, didn't measure too accurately), which is just about brushing up against GitHub's 14GB limit. One option would be to use a Large Runner, but in this case we seem to just about make it through the build itself, so we could "solve" it by deleting intermediate build products after the build. |
nightkr
added a commit
that referenced
this issue
Jun 19, 2024
Drop RPM, clean up intermediate files, avoid some copying Fixes #722
Merged
github-merge-queue bot
pushed a commit
that referenced
this issue
Jun 19, 2024
* Slim down Trino build Drop RPM, clean up intermediate files, avoid some copying Fixes #722 * Try deleting all source after Trino is built * Use tarball output to dedupe jars
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Caused by #687, see https://github.com/stackabletech/docker-images/actions/runs/9546922567
The text was updated successfully, but these errors were encountered: