On Sat, Feb 21, 2015 at 9:42 PM, Jody Garnett
wrote:
> I wondered if master and 13.x were tripping on each other resulting in a
> larger upload or something?
I did not see that in the logs, but was not searching for it either. That
said... how is larger uploads
relating to memory usage, it's be
I wondered if master and 13.x were tripping on each other resulting in a
larger upload or something?
On Sat, Feb 21, 2015 at 12:37 PM Andrea Aime
wrote:
> That did not work, but changing the maven memory from 512 to 768MB in the
> global
> settings apparently did the trick.
> I hope this won't en
That did not work, but changing the maven memory from 512 to 768MB in the
global
settings apparently did the trick.
I hope this won't end up breaking other builds...
Cheers
Andrea
On Sat, Feb 21, 2015 at 7:15 PM, Andrea Aime
wrote:
> On Fri, Feb 20, 2015 at 7:07 PM, Ben Caradoc-Davies
> wrote
On Fri, Feb 20, 2015 at 7:07 PM, Ben Caradoc-Davies
wrote:
> On 20/02/15 20:48, Andrea Aime wrote:
>
>> How was the 13.x build generated?
>>
>
> I created a new Jenkins job by copying geotools-master and changing the
> git branch. The post-build scripts need to be changed to the stable
> version,
Copying master was correct (since that is where the code came from!)
I am really puzzled about why it is not working. This afternoon I will turn
off the 2.5.x builds, and juggle around website links for stable and
maintenance.
--
Jody
--
Jody Garnett
On 20 February 2015 at 10:07, Ben Caradoc-Dav
On 20/02/15 20:48, Andrea Aime wrote:
> How was the 13.x build generated?
I created a new Jenkins job by copying geotools-master and changing the
git branch. The post-build scripts need to be changed to the stable
version, but it is not getting that far.
With -Xmx1024, geotools-13.x got past th
On Fri, Feb 20, 2015 at 12:09 AM, Jody Garnett
wrote:
> Checking, I also do not see any difference between the two.
>
>
Hi,
I did raise the memory given to javadoc in order to allow building master
javadocs some time
ago... but I don't remember exactly if I changed the build in jenkins, or
the po
Checking, I also do not see any difference between the two.
--
Jody Garnett
On 19 February 2015 at 14:35, Ben Caradoc-Davies wrote:
> Jody,
>
> after 3 attempts and -Xmx1024m I managed to get Jenkins geotools-13.x past
> the deploy phase, but not javadocs. I have now kicked geoserver and cite,
Jody,
after 3 attempts and -Xmx1024m I managed to get Jenkins geotools-13.x
past the deploy phase, but not javadocs. I have now kicked geoserver and
cite, and will proceed with 13-RC1, but I will need your advice and
assistance fixing this build. I do not understand why it fails and
geotools-m
