Re: [Geotools-devel] Build failed in Jenkins: geotools-16.x #1

Success! Build #3 passed without any extra JVM args. Was the extra memory really needed? A mystery. On 15/10/16 12:44, Ben Caradoc-Davies wrote: > This fixed the build. We have some new commits on 16.x, so I have undone > this change to see if the deploy step passes without it. > > On 15/10/16

Re: [Geotools-devel] Build failed in Jenkins: geotools-16.x #1

This fixed the build. We have some new commits on 16.x, so I have undone this change to see if the deploy step passes without it. On 15/10/16 10:00, Ben Caradoc-Davies wrote: > Failed in the deploy step. I set -Xmx1024m and kicked it. I seem to > recall that new builds sometimes require a little

Re: [Geotools-devel] Build failed in Jenkins: geotools-16.x #1

Failed in the deploy step. I set -Xmx1024m and kicked it. I seem to recall that new builds sometimes require a little help (and more memory) to get past the first build. We can then remove the JVM option. On 15/10/16 05:18, moni...@boundlessgeo.com wrote: > See

[Geotools-devel] Build failed in Jenkins: geotools-16.x #1

See -- [...truncated 22049 lines...] [INFO] Uploading: https://repo.boundlessgeo.com/snapshot/org/geotools/ogc/net.opengis.wcs/16-SNAPSHOT/net.opengis.wcs-16-20161014.161834-776.pom [INFO]