Menu
We've installed Gitlab on-premises, however someone else did the installation so I don't know as much about configuring the runners, etc. A pipeline failed due to the following error:
Uploading artifacts...
app/build/outputs/apk/debug/app-debug.apk: found 1 matching files
app/build/outputs/apk/androidTest/debug/app-debug-androidTest.apk: found 1 matching files
ERROR: Uploading artifacts to coordinator... too large archive id=13832 responseStatus=413 Request Entity Too Large status=413 Request Entity Too Large token=fCysmH9H
FATAL: Too large
ERROR: Job failed: exit code 1
Where/how do I configure the allowable artifact size?
429
The artifacts are stored by default in /home/git/gitlab/shared/artifacts . Save the file and restart GitLab for the changes to take effect.
Pipeline artifacts are files created by GitLab after a pipeline finishes. Pipeline artifacts are different to job artifacts because they are not explicitly managed by . gitlab-ci. yml definitions. Pipeline artifacts are used by the test coverage visualization feature to collect coverage information.
If you are an administrator, you can access the Admin Area by visiting /admin on your self-managed instance. You can also access it through the UI: GitLab versions 14.0 and later: on the top bar, select Menu > Admin. GitLab versions 13.12 and earlier: on the top bar, select the Admin Area icon ( ).
I was able to solve my problem after finding https://gitlab.com/gitlab-org/gitlab-runner/issues/2584. It suggests increasing maximum artifacts size on the on-prem instance of Gitlab. Here are the steps that worked for me:
Click Settings
https://gitlab.MYCOMPANY.com/admin/application_settings/ci_cd
Expand "Continuous Integration and Deployment"
This assumes your login credentials allow you to see the Admin Area.
169
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With