You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by Andrew Bayer <ab...@apache.org> on 2014/05/23 20:09:18 UTC
Latest status on the hanging Jenkins slaves/builds
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.
Re: Latest status on the hanging Jenkins slaves/builds
Posted by Lukasz Lenart <lu...@apache.org>.
2014-05-24 8:31 GMT+02:00 Hervé BOUTEMY <he...@free.fr>:
>> how we can share artifacts without directly linking to Jenkins
>> workspace.
> IIUC, now that workspace is not accessible for anonymous users, this is only a
> question of "it works" vs "it does not work" :)
Aha.... so I missed this out, how can I share the latest builds then
(for non-Maven users)?
Thanks in advance
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Re: Latest status on the hanging Jenkins slaves/builds
Posted by Hervé BOUTEMY <he...@free.fr>.
Le samedi 24 mai 2014 06:36:54 Lukasz Lenart a écrit :
> The better idea is to notify PMCs (pmcs@apache.org?) and send
> instructions how to convert Maven project into free-style project IMO.
> I can do it for Apache Struts project (6-8 builds) and probably others
> will likely do it for their projects - we want to have stable builds
and eventually provide regular reports on how much works remains to be done
I can help on this if not easily feasible with some Jenkins super-plugin
>
> :-)
>
> Also blog post how to configure jobs in the future will be useful
http://wiki.apache.org/general/Jenkins#Are_there_recommended_or_mandatory_Jenkins_settings_for_ASF_projects.3F
seems the right place
> and
> how we can share artifacts without directly linking to Jenkins
> workspace.
IIUC, now that workspace is not accessible for anonymous users, this is only a
question of "it works" vs "it does not work" :)
Regards
Hervé
>
>
> Regards
>
> > Does it make sense to start with disabling all maven plugin-based jobs
> > first to see if that helps with the hanging issue?* Purging 600 jobs
> > seems like a rash first step if we aren't certain that it is indeed
> > the problem.
> >
> > Obviously this will need lots of visibility prior to doing it, notice
> > on builds@, perhaps even a blog post.
> >
> > --David
> >
> > On Fri, May 23, 2014 at 2:09 PM, Andrew Bayer <ab...@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.
Re: Latest status on the hanging Jenkins slaves/builds
Posted by Lukasz Lenart <lu...@apache.org>.
The better idea is to notify PMCs (pmcs@apache.org?) and send
instructions how to convert Maven project into free-style project IMO.
I can do it for Apache Struts project (6-8 builds) and probably others
will likely do it for their projects - we want to have stable builds
:-)
Also blog post how to configure jobs in the future will be useful and
how we can share artifacts without directly linking to Jenkins
workspace.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2014-05-24 3:33 GMT+02:00 David Nalley <da...@gnsa.us>:
> Does it make sense to start with disabling all maven plugin-based jobs
> first to see if that helps with the hanging issue?* Purging 600 jobs
> seems like a rash first step if we aren't certain that it is indeed
> the problem.
>
> Obviously this will need lots of visibility prior to doing it, notice
> on builds@, perhaps even a blog post.
>
> --David
>
> On Fri, May 23, 2014 at 2:09 PM, Andrew Bayer <ab...@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.
Re: Latest status on the hanging Jenkins slaves/builds
Posted by David Nalley <da...@gnsa.us>.
Does it make sense to start with disabling all maven plugin-based jobs
first to see if that helps with the hanging issue?* Purging 600 jobs
seems like a rash first step if we aren't certain that it is indeed
the problem.
Obviously this will need lots of visibility prior to doing it, notice
on builds@, perhaps even a blog post.
--David
On Fri, May 23, 2014 at 2:09 PM, Andrew Bayer <ab...@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.
Re: Latest status on the hanging Jenkins slaves/builds
Posted by Hervé BOUTEMY <he...@free.fr>.
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
http://jenkins-ci.org/changelog
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
Regards,
Hervé
>
> Cheers
> --
> Olivier
>
> On May 24, 2014 4:10 AM, "Andrew Bayer" <ab...@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.
Re: Latest status on the hanging Jenkins slaves/builds
Posted by Olivier Lamy <ol...@apache.org>.
please start a new thread as it's definitely not the same problem.
On 26 May 2014 16:35, Tilman Hausherr <TH...@t-online.de> wrote:
> Now the repository server is gone:
> http://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox-app/
> brings an empty web page.
>
> Tilman
>
> Am 26.05.2014 06:15, schrieb Olivier Lamy:
>
>> 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 <an...@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" <ab...@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
Re: Latest status on the hanging Jenkins slaves/builds
Posted by Tilman Hausherr <TH...@t-online.de>.
Now the repository server is gone:
http://repository.apache.org/content/groups/snapshots/org/apache/pdfbox/pdfbox-app/
brings an empty web page.
Tilman
Am 26.05.2014 06:15, schrieb Olivier Lamy:
> 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 <an...@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" <ab...@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.
>
>
Re: Latest status on the hanging Jenkins slaves/builds
Posted by Andrew Bayer <an...@gmail.com>.
So far, at least, things are looking much better - the front page does take
a while to load initially, but I don't see any hanging jobs, which had been
cropping up in less time than this previously, and I don't see the polling
problems either...
A.
On Monday, May 26, 2014, Andrew Bayer <an...@gmail.com> wrote:
> Downgraded and restarted - let's see how things go now...
>
> A.
>
>
> On Mon, May 26, 2014 at 11:32 AM, Andrew Bayer <andrew.bayer@gmail.com<javascript:_e(%7B%7D,'cvml','andrew.bayer@gmail.com');>
> > wrote:
>
>> I'm starting work on moving to 1.554.1 - I'd really prefer to go with
>> 1.532.3, but there are just enough installed plugins that are newer than
>> 1.532 that I'll play it safe.
>>
>> A.
>>
>>
>> On Mon, May 26, 2014 at 10:28 AM, Andrew Bayer <andrew.bayer@gmail.com<javascript:_e(%7B%7D,'cvml','andrew.bayer@gmail.com');>
>> > wrote:
>>
>>> That's what's happening across all the slaves with Maven jobs.
>>>
>>> A.
>>>
>>>
>>> On Monday, May 26, 2014, Olivier Lamy <olamy@apache.org<javascript:_e(%7B%7D,'cvml','olamy@apache.org');>>
>>> wrote:
>>>
>>>> Note I have disabled ubuntu 5&6 nodes. As jobs were hanging on those
>>>> nodes.
>>>> Especially when installing artifacts locally, someone to have a look
>>>> if there any io issues on those servers?
>>>>
>>>> On 26 May 2014 14:15, Olivier Lamy <ol...@apache.org> wrote:
>>>> > 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 <an...@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" <ab...@apache.org> wrote:
>>>> >>>>
>>>> >>>> So I opened https://issues.jenkins-ci.org/browse/JENKINS-23098for 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
>>>>
>>>>
>>>>
>>>> --
>>>> Olivier Lamy
>>>> Ecetera: http://ecetera.com.au
>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>
>>>
>>
>
Re: Latest status on the hanging Jenkins slaves/builds
Posted by Andrew Bayer <an...@gmail.com>.
Downgraded and restarted - let's see how things go now...
A.
On Mon, May 26, 2014 at 11:32 AM, Andrew Bayer <an...@gmail.com>wrote:
> I'm starting work on moving to 1.554.1 - I'd really prefer to go with
> 1.532.3, but there are just enough installed plugins that are newer than
> 1.532 that I'll play it safe.
>
> A.
>
>
> On Mon, May 26, 2014 at 10:28 AM, Andrew Bayer <an...@gmail.com>wrote:
>
>> That's what's happening across all the slaves with Maven jobs.
>>
>> A.
>>
>>
>> On Monday, May 26, 2014, Olivier Lamy <ol...@apache.org> wrote:
>>
>>> Note I have disabled ubuntu 5&6 nodes. As jobs were hanging on those
>>> nodes.
>>> Especially when installing artifacts locally, someone to have a look
>>> if there any io issues on those servers?
>>>
>>> On 26 May 2014 14:15, Olivier Lamy <ol...@apache.org> wrote:
>>> > 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 <an...@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" <ab...@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
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Ecetera: http://ecetera.com.au
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>
>
Re: Latest status on the hanging Jenkins slaves/builds
Posted by Andrew Bayer <an...@gmail.com>.
I'm starting work on moving to 1.554.1 - I'd really prefer to go with
1.532.3, but there are just enough installed plugins that are newer than
1.532 that I'll play it safe.
A.
On Mon, May 26, 2014 at 10:28 AM, Andrew Bayer <an...@gmail.com>wrote:
> That's what's happening across all the slaves with Maven jobs.
>
> A.
>
>
> On Monday, May 26, 2014, Olivier Lamy <ol...@apache.org> wrote:
>
>> Note I have disabled ubuntu 5&6 nodes. As jobs were hanging on those
>> nodes.
>> Especially when installing artifacts locally, someone to have a look
>> if there any io issues on those servers?
>>
>> On 26 May 2014 14:15, Olivier Lamy <ol...@apache.org> wrote:
>> > 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 <an...@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" <ab...@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
>>
>>
>>
>> --
>> Olivier Lamy
>> Ecetera: http://ecetera.com.au
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>
Re: Latest status on the hanging Jenkins slaves/builds
Posted by Andrew Bayer <an...@gmail.com>.
That's what's happening across all the slaves with Maven jobs.
A.
On Monday, May 26, 2014, Olivier Lamy <ol...@apache.org> wrote:
> Note I have disabled ubuntu 5&6 nodes. As jobs were hanging on those nodes.
> Especially when installing artifacts locally, someone to have a look
> if there any io issues on those servers?
>
> On 26 May 2014 14:15, Olivier Lamy <olamy@apache.org <javascript:;>>
> wrote:
> > 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.bayer@gmail.com<javascript:;>>
> 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" <olamy@apache.org<javascript:;>>
> 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" <abayer@apache.org<javascript:;>>
> 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
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
Re: Latest status on the hanging Jenkins slaves/builds
Posted by Olivier Lamy <ol...@apache.org>.
Note I have disabled ubuntu 5&6 nodes. As jobs were hanging on those nodes.
Especially when installing artifacts locally, someone to have a look
if there any io issues on those servers?
On 26 May 2014 14:15, Olivier Lamy <ol...@apache.org> wrote:
> 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 <an...@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" <ab...@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
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Latest status on the hanging Jenkins slaves/builds
Posted by Olivier Lamy <ol...@apache.org>.
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 <an...@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" <ab...@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
Re: Latest status on the hanging Jenkins slaves/builds
Posted by Andrew Bayer <an...@gmail.com>.
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" <ab...@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.
>>
>
Re: Latest status on the hanging Jenkins slaves/builds
Posted by Olivier Lamy <ol...@apache.org>.
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" <ab...@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.
>