www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé BOUTEMY <herve.bout...@free.fr>
Subject Re: Latest status on the hanging Jenkins slaves/builds
Date Sat, 24 May 2014 06:43:09 GMT
Le samedi 24 mai 2014 14:51:47 Olivier Lamy a écrit :
> Out of the trendy tendance to say this plugin is crap :-)
> What is the real technical reason?
yes, I don't know the Jenkins dev community well, but there seems to be some 
hard words on this topic

as a user, another way of seeing the case is: what gives Jenkins Maven Plugin 
that freestyle project doesn't provide?

> 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.
the latest LTS isn't old: http://jenkins-ci.org/changelog-stable vs 

perhaps this will remove some risks (real or supposed): while stabilizing, 
being a little bit conservative can help, IMHO

> And revert back masters/slaves to java 1.7 ( I can do it Monday ).
is there anything making you think that JDK 8 can cause some trouble?
from time responses measure, the first improvements came when you said you 
upgraded everything to JDK8
but performance improvement isn't about stability: I have no proof of anything 
on stability



> Cheers
> --
> Olivier
> On May 24, 2014 4:10 AM, "Andrew Bayer" <abayer@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.

View raw message