Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: "Gav..." <gavin@16degrees.com.au>
To: <builds@apache.org>
References: <57EF1DBA-479D-443F-8CBC-966DDBD792FB@apache.org>
In-Reply-To: <57EF1DBA-479D-443F-8CBC-966DDBD792FB@apache.org>
Subject: RE: Hadoop patch builds for other Projects
Date: Sun, 3 Apr 2011 06:22:22 +1000
Message-ID: <02b901cbf173$ac8065e0$058131a0$@16degrees.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AQCwoHk8H2t3U9L5Ft7Fgfh0K61dBZaBpi7w
Content-Language: en-au


> -----Original Message-----
> From: Grant Ingersoll [mailto:gsingers@apache.org]
> Sent: Thursday, 31 March 2011 1:38 AM
> To: builds@apache.org
> Subject: Hadoop patch builds for other Projects
> 
> Over in Lucene, we interested in setting up a patch testing framework for
> Lucene similar to what Hadoop does.  That is, when a new patch comes in,
> we would like to apply it to the trunk, test it and check it if it meets
our
> requirements and then post a comment on the JIRA issue giving it a
> preliminary vote.
> 
> Does anyone know what the process is for setting this up?  Is there a wiki
or
> other instructions for it anywhere?  Or does, perhaps, Jenkins have a
plugin
> that supports this kind of thing?  As I recall from talking w/ Nigel about
this
> before, it involves a fair amount of scripting and some mail processing
work.

This was all setup I believe by Nigel and/or Doug so if they don't reply
here soon
feel free to ping them directly.

Gav...

> 
> Thanks,
> Grant