I've built several files that are to become artifacts. But, I get the following error:
Failed to execute plugin 'Artifact Copier' with error: java.io.IOException: Unexpected HTTP status code: 413 Request Too Long
Am I correct to say that this is a "file too big" error? Would I need my bamboo admin to change some http setting to allow me to upload larger artifacts? My IT guy might not know http well enough to know how to fix this. It would be great if I could pass this info on as well.
BTW, the error message I was getting is this one. check the quite explanatory empty part of it due to an exception on the agent. error 14-Apr-2015 22:39:36 Unable to publish artifact [myartifact]: error 14-Apr-2015 22:39:36 The artifact is required for down stream Stages and Jobs, build will now fail.
Found part of it. We have a nginx running in front of our tomcat for the bamboo server. Nginx has a default limitation size for HTTP requests. I bumped it up and these uploads worked for us.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are currently working through a similar issue at our company. Right now, it appears that it's probably our proxy limiting the request size. Here's a KB article dealing with a somewhat similar issue in JIRA: https://confluence.atlassian.com/display/JIRAKB/Attaching+a+File+Results+in+Request+Entity+Too+Large
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any news on this? I'm seeing the same error from one agent only and apparently for larger files (100MB). These files upload well from the other agents I have.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.