You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by Vinod Kumar Vavilapalli <vi...@hortonworks.com> on 2015/03/04 22:20:40 UTC
Reviving HADOOP-7435: Making Jenkins pre-commit build work with
branches
Hi all,
I'd like us to revive the effort at https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit builds being able to work with branches. Having the Jenkins verify patches on branches is very useful even if there may be relaxed review oversight on the said-branch.
Unless there are objections, I'd request help from Giri who already has a patch sitting there for more than a year before. This may need us to collectively agree on some convention - the last comment says that the branch patch name should be in some format for this to work.
Thanks,
+Vinod
Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with
branches
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
Tx for the feedback! Let's continue on JIRA, but I'd definitely welcome as much help as is available.
Thanks,
+Vinod
On Mar 4, 2015, at 3:30 PM, Zhijie Shen <zs...@hortonworks.com> wrote:
> +1. It¹s really helpful for branch development. To continue Karthik¹s
> point, is it good make pre-commit testing against branch-2 as the default
> too like that against trunk?
>
> On 3/4/15, 1:47 PM, "Sean Busbey" <bu...@cloudera.com> wrote:
>
>> +1
>>
>> If we can make things look like HBase support for precommit testing on
>> branches (HBASE-12944), that would make it easier for new and occasional
>> contributors who might end up working in other ecosystem projects. AFAICT,
>> Jonathan's proposal for branch names in patch names does this.
>>
>>
>>
>> On Wed, Mar 4, 2015 at 3:41 PM, Karthik Kambatla <ka...@cloudera.com>
>> wrote:
>>
>>> Thanks for reviving this on email, Vinod. Newer folks like me might not
>>> be
>>> aware of this JIRA/effort.
>>>
>>> This would be wonderful to have so (1) we know the status of release
>>> branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
>>> Jonathan's or Matt's proposal for including branch name looks
>>> reasonable to
>>> me.
>>>
>>> If none has any objections, I think we can continue on JIRA and get this
>>> in.
>>>
>>> On Wed, Mar 4, 2015 at 1:20 PM, Vinod Kumar Vavilapalli <
>>> vinodkv@hortonworks.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I'd like us to revive the effort at
>>>> https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit
>>>> builds being able to work with branches. Having the Jenkins verify
>>> patches
>>>> on branches is very useful even if there may be relaxed review
>>> oversight
>>> on
>>>> the said-branch.
>>>>
>>>> Unless there are objections, I'd request help from Giri who already
>>> has a
>>>> patch sitting there for more than a year before. This may need us to
>>>> collectively agree on some convention - the last comment says that the
>>>> branch patch name should be in some format for this to work.
>>>>
>>>> Thanks,
>>>> +Vinod
>>>>
>>>
>>>
>>>
>>> --
>>> Karthik Kambatla
>>> Software Engineer, Cloudera Inc.
>>> --------------------------------------------
>>> http://five.sentenc.es
>>>
>>
>>
>>
>> --
>> Sean
>
Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with
branches
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
Tx for the feedback! Let's continue on JIRA, but I'd definitely welcome as much help as is available.
Thanks,
+Vinod
On Mar 4, 2015, at 3:30 PM, Zhijie Shen <zs...@hortonworks.com> wrote:
> +1. It¹s really helpful for branch development. To continue Karthik¹s
> point, is it good make pre-commit testing against branch-2 as the default
> too like that against trunk?
>
> On 3/4/15, 1:47 PM, "Sean Busbey" <bu...@cloudera.com> wrote:
>
>> +1
>>
>> If we can make things look like HBase support for precommit testing on
>> branches (HBASE-12944), that would make it easier for new and occasional
>> contributors who might end up working in other ecosystem projects. AFAICT,
>> Jonathan's proposal for branch names in patch names does this.
>>
>>
>>
>> On Wed, Mar 4, 2015 at 3:41 PM, Karthik Kambatla <ka...@cloudera.com>
>> wrote:
>>
>>> Thanks for reviving this on email, Vinod. Newer folks like me might not
>>> be
>>> aware of this JIRA/effort.
>>>
>>> This would be wonderful to have so (1) we know the status of release
>>> branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
>>> Jonathan's or Matt's proposal for including branch name looks
>>> reasonable to
>>> me.
>>>
>>> If none has any objections, I think we can continue on JIRA and get this
>>> in.
>>>
>>> On Wed, Mar 4, 2015 at 1:20 PM, Vinod Kumar Vavilapalli <
>>> vinodkv@hortonworks.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I'd like us to revive the effort at
>>>> https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit
>>>> builds being able to work with branches. Having the Jenkins verify
>>> patches
>>>> on branches is very useful even if there may be relaxed review
>>> oversight
>>> on
>>>> the said-branch.
>>>>
>>>> Unless there are objections, I'd request help from Giri who already
>>> has a
>>>> patch sitting there for more than a year before. This may need us to
>>>> collectively agree on some convention - the last comment says that the
>>>> branch patch name should be in some format for this to work.
>>>>
>>>> Thanks,
>>>> +Vinod
>>>>
>>>
>>>
>>>
>>> --
>>> Karthik Kambatla
>>> Software Engineer, Cloudera Inc.
>>> --------------------------------------------
>>> http://five.sentenc.es
>>>
>>
>>
>>
>> --
>> Sean
>
Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with
branches
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
Tx for the feedback! Let's continue on JIRA, but I'd definitely welcome as much help as is available.
Thanks,
+Vinod
On Mar 4, 2015, at 3:30 PM, Zhijie Shen <zs...@hortonworks.com> wrote:
> +1. It¹s really helpful for branch development. To continue Karthik¹s
> point, is it good make pre-commit testing against branch-2 as the default
> too like that against trunk?
>
> On 3/4/15, 1:47 PM, "Sean Busbey" <bu...@cloudera.com> wrote:
>
>> +1
>>
>> If we can make things look like HBase support for precommit testing on
>> branches (HBASE-12944), that would make it easier for new and occasional
>> contributors who might end up working in other ecosystem projects. AFAICT,
>> Jonathan's proposal for branch names in patch names does this.
>>
>>
>>
>> On Wed, Mar 4, 2015 at 3:41 PM, Karthik Kambatla <ka...@cloudera.com>
>> wrote:
>>
>>> Thanks for reviving this on email, Vinod. Newer folks like me might not
>>> be
>>> aware of this JIRA/effort.
>>>
>>> This would be wonderful to have so (1) we know the status of release
>>> branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
>>> Jonathan's or Matt's proposal for including branch name looks
>>> reasonable to
>>> me.
>>>
>>> If none has any objections, I think we can continue on JIRA and get this
>>> in.
>>>
>>> On Wed, Mar 4, 2015 at 1:20 PM, Vinod Kumar Vavilapalli <
>>> vinodkv@hortonworks.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I'd like us to revive the effort at
>>>> https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit
>>>> builds being able to work with branches. Having the Jenkins verify
>>> patches
>>>> on branches is very useful even if there may be relaxed review
>>> oversight
>>> on
>>>> the said-branch.
>>>>
>>>> Unless there are objections, I'd request help from Giri who already
>>> has a
>>>> patch sitting there for more than a year before. This may need us to
>>>> collectively agree on some convention - the last comment says that the
>>>> branch patch name should be in some format for this to work.
>>>>
>>>> Thanks,
>>>> +Vinod
>>>>
>>>
>>>
>>>
>>> --
>>> Karthik Kambatla
>>> Software Engineer, Cloudera Inc.
>>> --------------------------------------------
>>> http://five.sentenc.es
>>>
>>
>>
>>
>> --
>> Sean
>
Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with
branches
Posted by Vinod Kumar Vavilapalli <vi...@hortonworks.com>.
Tx for the feedback! Let's continue on JIRA, but I'd definitely welcome as much help as is available.
Thanks,
+Vinod
On Mar 4, 2015, at 3:30 PM, Zhijie Shen <zs...@hortonworks.com> wrote:
> +1. It¹s really helpful for branch development. To continue Karthik¹s
> point, is it good make pre-commit testing against branch-2 as the default
> too like that against trunk?
>
> On 3/4/15, 1:47 PM, "Sean Busbey" <bu...@cloudera.com> wrote:
>
>> +1
>>
>> If we can make things look like HBase support for precommit testing on
>> branches (HBASE-12944), that would make it easier for new and occasional
>> contributors who might end up working in other ecosystem projects. AFAICT,
>> Jonathan's proposal for branch names in patch names does this.
>>
>>
>>
>> On Wed, Mar 4, 2015 at 3:41 PM, Karthik Kambatla <ka...@cloudera.com>
>> wrote:
>>
>>> Thanks for reviving this on email, Vinod. Newer folks like me might not
>>> be
>>> aware of this JIRA/effort.
>>>
>>> This would be wonderful to have so (1) we know the status of release
>>> branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
>>> Jonathan's or Matt's proposal for including branch name looks
>>> reasonable to
>>> me.
>>>
>>> If none has any objections, I think we can continue on JIRA and get this
>>> in.
>>>
>>> On Wed, Mar 4, 2015 at 1:20 PM, Vinod Kumar Vavilapalli <
>>> vinodkv@hortonworks.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I'd like us to revive the effort at
>>>> https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit
>>>> builds being able to work with branches. Having the Jenkins verify
>>> patches
>>>> on branches is very useful even if there may be relaxed review
>>> oversight
>>> on
>>>> the said-branch.
>>>>
>>>> Unless there are objections, I'd request help from Giri who already
>>> has a
>>>> patch sitting there for more than a year before. This may need us to
>>>> collectively agree on some convention - the last comment says that the
>>>> branch patch name should be in some format for this to work.
>>>>
>>>> Thanks,
>>>> +Vinod
>>>>
>>>
>>>
>>>
>>> --
>>> Karthik Kambatla
>>> Software Engineer, Cloudera Inc.
>>> --------------------------------------------
>>> http://five.sentenc.es
>>>
>>
>>
>>
>> --
>> Sean
>
Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with
branches
Posted by Zhijie Shen <zs...@hortonworks.com>.
+1. It¹s really helpful for branch development. To continue Karthik¹s
point, is it good make pre-commit testing against branch-2 as the default
too like that against trunk?
On 3/4/15, 1:47 PM, "Sean Busbey" <bu...@cloudera.com> wrote:
>+1
>
>If we can make things look like HBase support for precommit testing on
>branches (HBASE-12944), that would make it easier for new and occasional
>contributors who might end up working in other ecosystem projects. AFAICT,
>Jonathan's proposal for branch names in patch names does this.
>
>
>
>On Wed, Mar 4, 2015 at 3:41 PM, Karthik Kambatla <ka...@cloudera.com>
>wrote:
>
>> Thanks for reviving this on email, Vinod. Newer folks like me might not
>>be
>> aware of this JIRA/effort.
>>
>> This would be wonderful to have so (1) we know the status of release
>> branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
>> Jonathan's or Matt's proposal for including branch name looks
>>reasonable to
>> me.
>>
>> If none has any objections, I think we can continue on JIRA and get this
>> in.
>>
>> On Wed, Mar 4, 2015 at 1:20 PM, Vinod Kumar Vavilapalli <
>> vinodkv@hortonworks.com> wrote:
>>
>> > Hi all,
>> >
>> > I'd like us to revive the effort at
>> > https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit
>> > builds being able to work with branches. Having the Jenkins verify
>> patches
>> > on branches is very useful even if there may be relaxed review
>>oversight
>> on
>> > the said-branch.
>> >
>> > Unless there are objections, I'd request help from Giri who already
>>has a
>> > patch sitting there for more than a year before. This may need us to
>> > collectively agree on some convention - the last comment says that the
>> > branch patch name should be in some format for this to work.
>> >
>> > Thanks,
>> > +Vinod
>> >
>>
>>
>>
>> --
>> Karthik Kambatla
>> Software Engineer, Cloudera Inc.
>> --------------------------------------------
>> http://five.sentenc.es
>>
>
>
>
>--
>Sean
Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with
branches
Posted by Zhijie Shen <zs...@hortonworks.com>.
+1. It¹s really helpful for branch development. To continue Karthik¹s
point, is it good make pre-commit testing against branch-2 as the default
too like that against trunk?
On 3/4/15, 1:47 PM, "Sean Busbey" <bu...@cloudera.com> wrote:
>+1
>
>If we can make things look like HBase support for precommit testing on
>branches (HBASE-12944), that would make it easier for new and occasional
>contributors who might end up working in other ecosystem projects. AFAICT,
>Jonathan's proposal for branch names in patch names does this.
>
>
>
>On Wed, Mar 4, 2015 at 3:41 PM, Karthik Kambatla <ka...@cloudera.com>
>wrote:
>
>> Thanks for reviving this on email, Vinod. Newer folks like me might not
>>be
>> aware of this JIRA/effort.
>>
>> This would be wonderful to have so (1) we know the status of release
>> branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
>> Jonathan's or Matt's proposal for including branch name looks
>>reasonable to
>> me.
>>
>> If none has any objections, I think we can continue on JIRA and get this
>> in.
>>
>> On Wed, Mar 4, 2015 at 1:20 PM, Vinod Kumar Vavilapalli <
>> vinodkv@hortonworks.com> wrote:
>>
>> > Hi all,
>> >
>> > I'd like us to revive the effort at
>> > https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit
>> > builds being able to work with branches. Having the Jenkins verify
>> patches
>> > on branches is very useful even if there may be relaxed review
>>oversight
>> on
>> > the said-branch.
>> >
>> > Unless there are objections, I'd request help from Giri who already
>>has a
>> > patch sitting there for more than a year before. This may need us to
>> > collectively agree on some convention - the last comment says that the
>> > branch patch name should be in some format for this to work.
>> >
>> > Thanks,
>> > +Vinod
>> >
>>
>>
>>
>> --
>> Karthik Kambatla
>> Software Engineer, Cloudera Inc.
>> --------------------------------------------
>> http://five.sentenc.es
>>
>
>
>
>--
>Sean
Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with
branches
Posted by Zhijie Shen <zs...@hortonworks.com>.
+1. It¹s really helpful for branch development. To continue Karthik¹s
point, is it good make pre-commit testing against branch-2 as the default
too like that against trunk?
On 3/4/15, 1:47 PM, "Sean Busbey" <bu...@cloudera.com> wrote:
>+1
>
>If we can make things look like HBase support for precommit testing on
>branches (HBASE-12944), that would make it easier for new and occasional
>contributors who might end up working in other ecosystem projects. AFAICT,
>Jonathan's proposal for branch names in patch names does this.
>
>
>
>On Wed, Mar 4, 2015 at 3:41 PM, Karthik Kambatla <ka...@cloudera.com>
>wrote:
>
>> Thanks for reviving this on email, Vinod. Newer folks like me might not
>>be
>> aware of this JIRA/effort.
>>
>> This would be wonderful to have so (1) we know the status of release
>> branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
>> Jonathan's or Matt's proposal for including branch name looks
>>reasonable to
>> me.
>>
>> If none has any objections, I think we can continue on JIRA and get this
>> in.
>>
>> On Wed, Mar 4, 2015 at 1:20 PM, Vinod Kumar Vavilapalli <
>> vinodkv@hortonworks.com> wrote:
>>
>> > Hi all,
>> >
>> > I'd like us to revive the effort at
>> > https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit
>> > builds being able to work with branches. Having the Jenkins verify
>> patches
>> > on branches is very useful even if there may be relaxed review
>>oversight
>> on
>> > the said-branch.
>> >
>> > Unless there are objections, I'd request help from Giri who already
>>has a
>> > patch sitting there for more than a year before. This may need us to
>> > collectively agree on some convention - the last comment says that the
>> > branch patch name should be in some format for this to work.
>> >
>> > Thanks,
>> > +Vinod
>> >
>>
>>
>>
>> --
>> Karthik Kambatla
>> Software Engineer, Cloudera Inc.
>> --------------------------------------------
>> http://five.sentenc.es
>>
>
>
>
>--
>Sean
Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with
branches
Posted by Zhijie Shen <zs...@hortonworks.com>.
+1. It¹s really helpful for branch development. To continue Karthik¹s
point, is it good make pre-commit testing against branch-2 as the default
too like that against trunk?
On 3/4/15, 1:47 PM, "Sean Busbey" <bu...@cloudera.com> wrote:
>+1
>
>If we can make things look like HBase support for precommit testing on
>branches (HBASE-12944), that would make it easier for new and occasional
>contributors who might end up working in other ecosystem projects. AFAICT,
>Jonathan's proposal for branch names in patch names does this.
>
>
>
>On Wed, Mar 4, 2015 at 3:41 PM, Karthik Kambatla <ka...@cloudera.com>
>wrote:
>
>> Thanks for reviving this on email, Vinod. Newer folks like me might not
>>be
>> aware of this JIRA/effort.
>>
>> This would be wonderful to have so (1) we know the status of release
>> branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
>> Jonathan's or Matt's proposal for including branch name looks
>>reasonable to
>> me.
>>
>> If none has any objections, I think we can continue on JIRA and get this
>> in.
>>
>> On Wed, Mar 4, 2015 at 1:20 PM, Vinod Kumar Vavilapalli <
>> vinodkv@hortonworks.com> wrote:
>>
>> > Hi all,
>> >
>> > I'd like us to revive the effort at
>> > https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit
>> > builds being able to work with branches. Having the Jenkins verify
>> patches
>> > on branches is very useful even if there may be relaxed review
>>oversight
>> on
>> > the said-branch.
>> >
>> > Unless there are objections, I'd request help from Giri who already
>>has a
>> > patch sitting there for more than a year before. This may need us to
>> > collectively agree on some convention - the last comment says that the
>> > branch patch name should be in some format for this to work.
>> >
>> > Thanks,
>> > +Vinod
>> >
>>
>>
>>
>> --
>> Karthik Kambatla
>> Software Engineer, Cloudera Inc.
>> --------------------------------------------
>> http://five.sentenc.es
>>
>
>
>
>--
>Sean
Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with branches
Posted by Sean Busbey <bu...@cloudera.com>.
+1
If we can make things look like HBase support for precommit testing on
branches (HBASE-12944), that would make it easier for new and occasional
contributors who might end up working in other ecosystem projects. AFAICT,
Jonathan's proposal for branch names in patch names does this.
On Wed, Mar 4, 2015 at 3:41 PM, Karthik Kambatla <ka...@cloudera.com> wrote:
> Thanks for reviving this on email, Vinod. Newer folks like me might not be
> aware of this JIRA/effort.
>
> This would be wonderful to have so (1) we know the status of release
> branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
> Jonathan's or Matt's proposal for including branch name looks reasonable to
> me.
>
> If none has any objections, I think we can continue on JIRA and get this
> in.
>
> On Wed, Mar 4, 2015 at 1:20 PM, Vinod Kumar Vavilapalli <
> vinodkv@hortonworks.com> wrote:
>
> > Hi all,
> >
> > I'd like us to revive the effort at
> > https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit
> > builds being able to work with branches. Having the Jenkins verify
> patches
> > on branches is very useful even if there may be relaxed review oversight
> on
> > the said-branch.
> >
> > Unless there are objections, I'd request help from Giri who already has a
> > patch sitting there for more than a year before. This may need us to
> > collectively agree on some convention - the last comment says that the
> > branch patch name should be in some format for this to work.
> >
> > Thanks,
> > +Vinod
> >
>
>
>
> --
> Karthik Kambatla
> Software Engineer, Cloudera Inc.
> --------------------------------------------
> http://five.sentenc.es
>
--
Sean
Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with branches
Posted by Sean Busbey <bu...@cloudera.com>.
+1
If we can make things look like HBase support for precommit testing on
branches (HBASE-12944), that would make it easier for new and occasional
contributors who might end up working in other ecosystem projects. AFAICT,
Jonathan's proposal for branch names in patch names does this.
On Wed, Mar 4, 2015 at 3:41 PM, Karthik Kambatla <ka...@cloudera.com> wrote:
> Thanks for reviving this on email, Vinod. Newer folks like me might not be
> aware of this JIRA/effort.
>
> This would be wonderful to have so (1) we know the status of release
> branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
> Jonathan's or Matt's proposal for including branch name looks reasonable to
> me.
>
> If none has any objections, I think we can continue on JIRA and get this
> in.
>
> On Wed, Mar 4, 2015 at 1:20 PM, Vinod Kumar Vavilapalli <
> vinodkv@hortonworks.com> wrote:
>
> > Hi all,
> >
> > I'd like us to revive the effort at
> > https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit
> > builds being able to work with branches. Having the Jenkins verify
> patches
> > on branches is very useful even if there may be relaxed review oversight
> on
> > the said-branch.
> >
> > Unless there are objections, I'd request help from Giri who already has a
> > patch sitting there for more than a year before. This may need us to
> > collectively agree on some convention - the last comment says that the
> > branch patch name should be in some format for this to work.
> >
> > Thanks,
> > +Vinod
> >
>
>
>
> --
> Karthik Kambatla
> Software Engineer, Cloudera Inc.
> --------------------------------------------
> http://five.sentenc.es
>
--
Sean
Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with branches
Posted by Sean Busbey <bu...@cloudera.com>.
+1
If we can make things look like HBase support for precommit testing on
branches (HBASE-12944), that would make it easier for new and occasional
contributors who might end up working in other ecosystem projects. AFAICT,
Jonathan's proposal for branch names in patch names does this.
On Wed, Mar 4, 2015 at 3:41 PM, Karthik Kambatla <ka...@cloudera.com> wrote:
> Thanks for reviving this on email, Vinod. Newer folks like me might not be
> aware of this JIRA/effort.
>
> This would be wonderful to have so (1) we know the status of release
> branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
> Jonathan's or Matt's proposal for including branch name looks reasonable to
> me.
>
> If none has any objections, I think we can continue on JIRA and get this
> in.
>
> On Wed, Mar 4, 2015 at 1:20 PM, Vinod Kumar Vavilapalli <
> vinodkv@hortonworks.com> wrote:
>
> > Hi all,
> >
> > I'd like us to revive the effort at
> > https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit
> > builds being able to work with branches. Having the Jenkins verify
> patches
> > on branches is very useful even if there may be relaxed review oversight
> on
> > the said-branch.
> >
> > Unless there are objections, I'd request help from Giri who already has a
> > patch sitting there for more than a year before. This may need us to
> > collectively agree on some convention - the last comment says that the
> > branch patch name should be in some format for this to work.
> >
> > Thanks,
> > +Vinod
> >
>
>
>
> --
> Karthik Kambatla
> Software Engineer, Cloudera Inc.
> --------------------------------------------
> http://five.sentenc.es
>
--
Sean
Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with branches
Posted by Sean Busbey <bu...@cloudera.com>.
+1
If we can make things look like HBase support for precommit testing on
branches (HBASE-12944), that would make it easier for new and occasional
contributors who might end up working in other ecosystem projects. AFAICT,
Jonathan's proposal for branch names in patch names does this.
On Wed, Mar 4, 2015 at 3:41 PM, Karthik Kambatla <ka...@cloudera.com> wrote:
> Thanks for reviving this on email, Vinod. Newer folks like me might not be
> aware of this JIRA/effort.
>
> This would be wonderful to have so (1) we know the status of release
> branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
> Jonathan's or Matt's proposal for including branch name looks reasonable to
> me.
>
> If none has any objections, I think we can continue on JIRA and get this
> in.
>
> On Wed, Mar 4, 2015 at 1:20 PM, Vinod Kumar Vavilapalli <
> vinodkv@hortonworks.com> wrote:
>
> > Hi all,
> >
> > I'd like us to revive the effort at
> > https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit
> > builds being able to work with branches. Having the Jenkins verify
> patches
> > on branches is very useful even if there may be relaxed review oversight
> on
> > the said-branch.
> >
> > Unless there are objections, I'd request help from Giri who already has a
> > patch sitting there for more than a year before. This may need us to
> > collectively agree on some convention - the last comment says that the
> > branch patch name should be in some format for this to work.
> >
> > Thanks,
> > +Vinod
> >
>
>
>
> --
> Karthik Kambatla
> Software Engineer, Cloudera Inc.
> --------------------------------------------
> http://five.sentenc.es
>
--
Sean
Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with branches
Posted by Karthik Kambatla <ka...@cloudera.com>.
Thanks for reviving this on email, Vinod. Newer folks like me might not be
aware of this JIRA/effort.
This would be wonderful to have so (1) we know the status of release
branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
Jonathan's or Matt's proposal for including branch name looks reasonable to
me.
If none has any objections, I think we can continue on JIRA and get this
in.
On Wed, Mar 4, 2015 at 1:20 PM, Vinod Kumar Vavilapalli <
vinodkv@hortonworks.com> wrote:
> Hi all,
>
> I'd like us to revive the effort at
> https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit
> builds being able to work with branches. Having the Jenkins verify patches
> on branches is very useful even if there may be relaxed review oversight on
> the said-branch.
>
> Unless there are objections, I'd request help from Giri who already has a
> patch sitting there for more than a year before. This may need us to
> collectively agree on some convention - the last comment says that the
> branch patch name should be in some format for this to work.
>
> Thanks,
> +Vinod
>
--
Karthik Kambatla
Software Engineer, Cloudera Inc.
--------------------------------------------
http://five.sentenc.es
Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with branches
Posted by Karthik Kambatla <ka...@cloudera.com>.
Thanks for reviving this on email, Vinod. Newer folks like me might not be
aware of this JIRA/effort.
This would be wonderful to have so (1) we know the status of release
branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
Jonathan's or Matt's proposal for including branch name looks reasonable to
me.
If none has any objections, I think we can continue on JIRA and get this
in.
On Wed, Mar 4, 2015 at 1:20 PM, Vinod Kumar Vavilapalli <
vinodkv@hortonworks.com> wrote:
> Hi all,
>
> I'd like us to revive the effort at
> https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit
> builds being able to work with branches. Having the Jenkins verify patches
> on branches is very useful even if there may be relaxed review oversight on
> the said-branch.
>
> Unless there are objections, I'd request help from Giri who already has a
> patch sitting there for more than a year before. This may need us to
> collectively agree on some convention - the last comment says that the
> branch patch name should be in some format for this to work.
>
> Thanks,
> +Vinod
>
--
Karthik Kambatla
Software Engineer, Cloudera Inc.
--------------------------------------------
http://five.sentenc.es
Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with branches
Posted by Karthik Kambatla <ka...@cloudera.com>.
Thanks for reviving this on email, Vinod. Newer folks like me might not be
aware of this JIRA/effort.
This would be wonderful to have so (1) we know the status of release
branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
Jonathan's or Matt's proposal for including branch name looks reasonable to
me.
If none has any objections, I think we can continue on JIRA and get this
in.
On Wed, Mar 4, 2015 at 1:20 PM, Vinod Kumar Vavilapalli <
vinodkv@hortonworks.com> wrote:
> Hi all,
>
> I'd like us to revive the effort at
> https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit
> builds being able to work with branches. Having the Jenkins verify patches
> on branches is very useful even if there may be relaxed review oversight on
> the said-branch.
>
> Unless there are objections, I'd request help from Giri who already has a
> patch sitting there for more than a year before. This may need us to
> collectively agree on some convention - the last comment says that the
> branch patch name should be in some format for this to work.
>
> Thanks,
> +Vinod
>
--
Karthik Kambatla
Software Engineer, Cloudera Inc.
--------------------------------------------
http://five.sentenc.es
Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with branches
Posted by Karthik Kambatla <ka...@cloudera.com>.
Thanks for reviving this on email, Vinod. Newer folks like me might not be
aware of this JIRA/effort.
This would be wonderful to have so (1) we know the status of release
branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
Jonathan's or Matt's proposal for including branch name looks reasonable to
me.
If none has any objections, I think we can continue on JIRA and get this
in.
On Wed, Mar 4, 2015 at 1:20 PM, Vinod Kumar Vavilapalli <
vinodkv@hortonworks.com> wrote:
> Hi all,
>
> I'd like us to revive the effort at
> https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit
> builds being able to work with branches. Having the Jenkins verify patches
> on branches is very useful even if there may be relaxed review oversight on
> the said-branch.
>
> Unless there are objections, I'd request help from Giri who already has a
> patch sitting there for more than a year before. This may need us to
> collectively agree on some convention - the last comment says that the
> branch patch name should be in some format for this to work.
>
> Thanks,
> +Vinod
>
--
Karthik Kambatla
Software Engineer, Cloudera Inc.
--------------------------------------------
http://five.sentenc.es