Just a disclaimer, I am an IT person not a developer so I made need a bit more explicit explanations than you are used to... I apologize in advance.
I am being asked to fix an issue with one of our deployment jobs in Jenkins
. The deploy job uses a chef cookbook and knife to .zip
the compiled .wars and then copies the .zip
to the test server. The job was previously working but the project files have grown much bigger and now when we run the job it fails to copy the .zip
file when running the batch script.
It fails with the error
ERROR: NoMemoryError: failed to allocate memory
This is really strange because our Jenkins server has plenty of ram... I checked utilization while running the job and it doesn't go over 4-6GB total and we have 24gb assigned to the virtual machine that hosts Jenkins.
This seems to be some sort of artificial limitation because if I manually build the .zip
and eliminate all the imported library .dlls
and reduce the size of the zip
to under 500mb it works fine. But I would rather not mess with my developer's project files to reduce the size (they all get pulled down from BitBucket when the job builds the source... I have no idea what kind of downstream effects it might have to just remove them).
There has to be a way to get this to copy .zips
larger than 500mb... this is 2017, 500mb is a pitiful limitation.
Any ideas on how to troubleshoot further? Any specific log files I should be looking at on the Jenkins server? The console output is the only place I see anything, and all that tells me is the memory allocation error.