wojtek opened 2 years ago
|
|||||
Robin Shen changed state to 'Closed' 2 years ago
|
|||||
I am using below values.yaml and it works. Please check your custom deploy config to make sure your setting is taking effect.
The NPE when manually upload an artifact is a bug though which will be fixed in issue #917 |
|||||
OK, the problem was... weird and I think it boils down to 1dev sending everything as one request hence somewhat "arbitrary" 50M limit, which didn't match anything... but - we had |
Type |
Bug
|
Priority |
Normal
|
Assignee | |
Affected Versions |
Not Found
|
Issue Votes (0)
When tryinh to publish artifact bigger than 50M I'm getting error "413 Request Entity Too Large" from nginx
We are running custom k8s chart, so I already increased nginx's maximum body size in ingress:
nginx.ingress.kubernetes.io/proxy-body-size: 200m
but still the issue persists.I dug a bit in the sources of PublishArtifact step (https://github.com/theonedev/onedev/blob/main/server-core/src/main/java/io/onedev/server/buildspec/step/PublishArtifactStep.java#L76-L76) and it seems like a regular copy… (though, we are using Kubernetes Executor, so there's that).
I though that file size limit from the performance options may be the problem (though publication of artifacts smaller than 50M works just fine) but after increasing this option from 20M to 100M it still doesn't work. However, manual upload now doesn't complain about file size limit, though it fails when trying to submit form just the same:
Any hint where this 50M could be configured would be highly appreciated.