Go if you have a bit of time. I just finished to downgrade to jdk1.7.0_55 (master and ubuntu slaves). Furthermore I have increase memory for all slaves (the slave process is now using -Xmx1024m for all ubuntu slaves)
On 26 May 2014 11:16, Andrew Bayer <andrew.ba...@gmail.com> wrote: > Downgrading to the latest LTS definitely seems like a good idea. Do you want > to do that or should I? > > On May 23, 2014 9:51 PM, "Olivier Lamy" <ol...@apache.org> wrote: >> >> Out of the trendy tendance to say this plugin is crap :-) >> What is the real technical reason? >> I don't see any in the jira issue. >> Why we don't try using LTS? >> The current master is plenty of changes especially in the remoting >> library. >> And revert back masters/slaves to java 1.7 ( I can do it Monday ). >> >> Cheers >> -- >> Olivier >> >> On May 24, 2014 4:10 AM, "Andrew Bayer" <aba...@apache.org> wrote: >>> >>> So I opened https://issues.jenkins-ci.org/browse/JENKINS-23098 for this, >>> and am currently putting together the support bundle mentioned in it. But it >>> looks like there's a very real chance that the Maven plugin/job type is just >>> so thoroughly crap at scale that we need to get rid of it and move all jobs >>> to freestyle projects, using Maven build steps instead. >>> >>> If that turns out to be the only real option, it's going to be an ugly >>> transition, given that we have over 600 Maven projects from many different >>> projects, and there's no automatic way to transition those projects. I can >>> probably come up with something that'll do a pretty decent approximation of >>> that, but it wouldn't be perfect. We may want to consider tossing all the >>> Maven jobs, removing the Maven plugin, and having the projects rebuild the >>> jobs themselves. >>> >>> A. -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy
