DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Pipeline as a Service: How To Test Pipelines in GitLab
  • GitLab vs Jenkins: Which Is the Best CI/CD Tool?
  • Auto Deploy Spring Boot App Using GitLab CI/CD
  • Using Git Submodules With Gitlab CI/CD

Trending

  • Why Your Test Automation Is Always Behind the Code And the Architecture That Fixes It
  • Skills, Java 17, and Theme Accents
  • Migrate a Hardcoded LangGraph Agent to LaunchDarkly AI Configs in 20 Minutes
  • How to Save Money Using Custom LLMs for Specific Tasks
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. Deployment
  4. GitLab CI Runner Artifacts Size Error: ''Too Large Archive'' [Snippet]

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.

By 
Kevin Hooke user avatar
Kevin Hooke
·
Aug. 18, 18 · Code Snippet
Likes (1)
Comment
Save
Tweet
Share
13.4K Views

Join the DZone community and get the full member experience.

Join For Free

As 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 large

Hmm. 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:

Continuous Integration/Deployment GitLab

Published at DZone with permission of Kevin Hooke. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Pipeline as a Service: How To Test Pipelines in GitLab
  • GitLab vs Jenkins: Which Is the Best CI/CD Tool?
  • Auto Deploy Spring Boot App Using GitLab CI/CD
  • Using Git Submodules With Gitlab CI/CD

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook