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
Newsletter
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

  • To Switch, or Not to Switch the AI Model
  • Kill the Worker, Keep the Research: Build a Recoverable LangGraph Agent on Temporal
  • Building a Real Pipeline With senro: Monorepos, Caching, and Triggers
  • Rebuilding Elasticsearch Under Load: Unsafe Watermarks and a Sampling Blind Spot

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  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
·
Aug. 18, 18 · Code Snippet
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
13.7K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

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

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • 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