I believe the usual practice should be: 1. The trunk patch (if applicable) must pass automated Jenkins testing for trunk CI build, and code review. 2. The branch patch should have "ant -Dpatch.file=<path.patch> test-patch" run against it in the developer's build environment for the branch, and the passing results pasted into the jira; and pass code review again if different from the trunk patch.
--Matt On Fri, Aug 5, 2011 at 4:08 PM, Konstantin Boudnik <c...@apache.org> wrote: > Yes, with usual +1 vote thing. > > Cos > > On Fri, Aug 05, 2011 at 07:02PM, milind.bhandar...@emc.com wrote: > > Aha! > > > > In that case, is the local test-patch success sufficient for patches on > > branches ? > > > > - milind > > > > On 8/5/11 3:38 PM, "Giridharan Kesavan" <gkesa...@hortonworks.com> > wrote: > > > > >Milind, > > > > > >patch testing usually happens only on trunk > > > > > > > > >thanks, > > >Giri > > > > > >On Fri, Aug 5, 2011 at 3:11 PM, <milind.bhandar...@emc.com> wrote: > > > > > >> Hi folks, > > >> > > >> Now that the build machines are available again, I tried resubmitting > a > > >> patch to https://issues.apache.org/jira/browse/MAPREDUCE-2767. > However, > > >>it > > >> looks like it is not being picked up by CI. > > >> > > >> Is 0.22 branch excluded from hadoop CI ? > > >> > > >> > > >> * Milind > > >> > > >> --- > > >> Milind Bhandarkar > > >> Greenplum Labs, EMC > > >> (Disclaimer: Opinions expressed in this email are those of the author, > > >>and > > >> do not necessarily represent the views of any organization, past or > > >>present, > > >> the author might be affiliated with.) > > >> > > >