GitLab CI Runner Artifacts Size Error: ''Too Large Archive'' [Snippet]
This quick fix provides a solution to the error ''Too large'' when uploading artifacts for your GitLab CI pipeline.
Join the DZone community and get the full member experience.
Join For FreeAs part of putting together a GitLab CI pipeline to build a Python deployment for AWS Lambda, I ran into an issue with the size of the build dir that I'm zipping up ready for deployment:
Uploading artifacts...
./build: found 2543 matching files
ERROR: Uploading artifacts to coordinator... too large archive id=181 responseStatus=413 Request Entity Too Large status=413 Request Entity Too Large token=rtRUzgtp
FATAL: Too largeHmm. OK. A quick search found this post, which says there's a setting to increase the max build artifact size — it's under /admin/application_settings, in the Continuous Integration setting — looks like the default is 100MB, so let's bump that up and try again:
Topics:
devops,
gitlab,
continuous integration,
ci/cd,
pipelines,
errors
Published at DZone with permission of Kevin Hooke, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Comments