I'm using the bitbucketpipelines / bitbucket-upload-file: 0.3.2 pipe, and it always worked perfectly, but now I'm accusing the error:
✖ Failed to upload files ['xxxxx.war']. Status code: 413. Message: <html>
<head><title>413 Request Entity Too Large</title></head>
<body bgcolor="white">
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx</center>
</body>
</html>
As I said, funny that there was never a problem, but now the problem is always occurring.
updating:
I can't upload files larger than 10MB, neither by the api (via cUrl), nor by the download area of the site.
Thanks for the answer, so I tested it through the pipe that bitbucket offers and also via curl, it was giving an error at the time I created this ticket, but not even in the night time it came back and so far it's normal, the strange thing was that I did tests on day of the error with files less than 10 MB and it was ... more than that it gave an error, put an atlassian status page and there was nothing on it.
[]s
@Wilber Marcel da Silva thanks for raising this, this help us to do our best to keep an eye on API changes (looks like it could be temporary server issue) and to not do breaking changes without notifying.
Anyway, I'll report it.
If the case rise again, give us this feedback please with possible logs you can share publicly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Wilber Marcel da Silva please, could you share the output when using curl for example?
I've just managed to upload 24 MB file using ui and curl both..
Also, what file size do you have? Perhaps, there is anyway the limit we don't know about and should investigate.
Please, share also the pipeline log of pipe's execution. Perhaps , we may find some details there and perhaps we have a bug that should be fixed.
Also, I suspect this filesize increased within a time and now it cannot work. Let's investigate it.
Looking forward to hearing from you! Thanks
Regards, Galyna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As an option you also may look at the Git Large file storage doc and see if it is worth to use
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.