Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Received-SPF: neutral (nike.apache.org: 216.145.54.171 is neither permitted
 nor denied by domain of jnaisbit@yahoo-inc.com)
From: Jeffrey Naisbitt <jnaisbit@yahoo-inc.com>
To: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>
Date: Thu, 15 Sep 2011 09:52:53 -0700
Subject: Re: jenkins testing on 0.20.20x
Thread-Topic: jenkins testing on 0.20.20x
Thread-Index: Acxzx5+ej5X406g5QMugxHNF4z93tgAAElJz
Message-ID: <CA979795.F4B1%jnaisbit@yahoo-inc.com>
In-Reply-To: 
 <CANJr2=Gxy+yy+OS5-br13m9Zrh9XTE7zmYDEMXZKhBhiye7SBQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Most people working on the 0.20.20x branch prefer that you still run
test-patch manually and then post the results as a comment to the Jira.  If
the change is complicated enough, it's a good idea to run the tests and pos=
t
the results too.
-Jeff


On 9/15/11 11:49 AM, "Giridharan Kesavan" <gkesavan@hortonworks.com> wrote:

> Steve,
>=20
> At the moment patch testing through jenkins is automated only for trunk.
>=20
>=20
>=20
> On Thu, Sep 15, 2011 at 9:44 AM, Steve Loughran <stevel@apache.org> wrote=
:
>> If I have some patches for the 0.20.20x branch, how do I submit them so =
they
>> get applied and tested on that branch, rather than trunk. I have a patch
>> that I want to get in there, but the JIRA process doesn't like the
>> (unappliable to trunk patch). I could get the patch into trunk first and
>> backport it, but really you want both branches' patches auto-reviewed
>>=20
>=20
>=20