Return-Path: <builds-return-3761-apmail-builds-archive=apache.org@apache.org>
X-Original-To: apmail-builds-archive@minotaur.apache.org
Delivered-To: apmail-builds-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id BCC2711130
	for <apmail-builds-archive@minotaur.apache.org>;
 Sat, 24 May 2014 04:51:49 +0000 (UTC)
Received: (qmail 53235 invoked by uid 500); 24 May 2014 04:51:49 -0000
Delivered-To: apmail-builds-archive@apache.org
Received: (qmail 52512 invoked by uid 500); 24 May 2014 04:51:49 -0000
Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:builds-help@apache.org>
List-Unsubscribe: <mailto:builds-unsubscribe@apache.org>
List-Post: <mailto:builds@apache.org>
List-Id: <builds.apache.org>
Reply-To: builds@apache.org
Delivered-To: mailing list builds@apache.org
Received: (qmail 52490 invoked by uid 99); 24 May 2014 04:51:49 -0000
Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 24 May 2014 04:51:49 +0000
Received: from localhost (HELO mail-oa0-f42.google.com) (127.0.0.1)
  (smtp-auth username olamy, mechanism plain)
  by minotaur.apache.org (qpsmtpd/0.29) with ESMTP;
 Sat, 24 May 2014 04:51:48 +0000
Received: by mail-oa0-f42.google.com with SMTP id j17so6528913oag.29
        for <multiple recipients>; Fri, 23 May 2014 21:51:47 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.78.4 with SMTP id x4mr9670344obw.55.1400907107876; Fri,
 23 May 2014 21:51:47 -0700 (PDT)
Received: by 10.182.136.67 with HTTP; Fri, 23 May 2014 21:51:47 -0700 (PDT)
Received: by 10.182.136.67 with HTTP; Fri, 23 May 2014 21:51:47 -0700 (PDT)
In-Reply-To: 
 <CAPbPdOZc2wzTNZU4vTW18TS1gt3MVbO55xnfh=4Op5khEaKa_A@mail.gmail.com>
References: 
 <CAPbPdOZc2wzTNZU4vTW18TS1gt3MVbO55xnfh=4Op5khEaKa_A@mail.gmail.com>
Date: Sat, 24 May 2014 14:51:47 +1000
Message-ID: 
 <CAPoyBqSLCgWnqwaNPjBgkiUWw4RATe9XtbU=UhF2CJAhZL0_9w@mail.gmail.com>
Subject: Re: Latest status on the hanging Jenkins slaves/builds
From: Olivier Lamy <olamy@apache.org>
To: Andrew Bayer <abayer@apache.org>
Cc: Apache Infrastructure <infrastructure@apache.org>, builds@apache.org
Content-Type: multipart/alternative; boundary=047d7b2e4a4a8752fb04fa1e1aca

--047d7b2e4a4a8752fb04fa1e1aca
Content-Type: text/plain; charset=UTF-8

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> 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.
>

--047d7b2e4a4a8752fb04fa1e1aca--