Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
Received-SPF: pass (nike.apache.org: domain of yzhang@cloudera.com designates
 209.85.218.44 as permitted sender)
MIME-Version: 1.0
Date: Fri, 14 Nov 2014 14:40:47 -0800
Message-ID: 
 <CAA0W1bSsE7Ztx33fThPUd1NtJNegkKpKfbvhqcagbQQdUenQJg@mail.gmail.com>
Subject: Re: submitting a hadoop patch doesn't trigger jenkins test run
From: Yongjun Zhang <yzhang@cloudera.com>
To: common-dev@hadoop.apache.org
Cc: "builds@apache.org" <builds@apache.org>
Content-Type: multipart/alternative; boundary=089e01184810ec1d0a0507d951c9

--089e01184810ec1d0a0507d951c9
Content-Type: text/plain; charset=UTF-8

Many thanks Ray, good to know!

--Yongjun

On Fri, Nov 14, 2014 at 2:03 PM, Ray Chiang <rchiang@cloudera.com> wrote:

> Your patch covers multiple projects (I see 81 files across
> hadoop-common-project, hadoop-hdfs-project, hadoop-mapreduce-project,
> hadoop-tools, hadoop-yarn-project).
>
> Jenkins had problems with that for me a few months back.  If you break it
> up per-project, it should work just fine.
>
> -Ray
>
>
> On Fri, Nov 14, 2014 at 1:49 PM, Ted Yu <yuzhihong@gmail.com> wrote:
>
> > Adding builds@apache
> >
> > On Fri, Nov 14, 2014 at 1:34 PM, Yongjun Zhang <yzhang@cloudera.com>
> > wrote:
> >
> > > Hi,
> > >
> > > One issue to report here, any help would be greatly appreciated!
> > >
> > > I noticed that multiple patch submissions to
> > > https://issues.apache.org/jira/browse/HADOOP-11293
> > > did not trigger jenkins test run.
> > >
> > > Thanks Chris Nauroth for the help to trigger one manually for me:
> > >
> > > https://builds.apache.org/job/PreCommit-HADOOP-Build/5079/
> > >
> > > and it turned out the manually triggered one did not report result back
> > to
> > > the jira upon finishing.
> > >
> > > I submitted the same patch to another jira (HADOOP-11045) that I was
> > > working on, which triggered jenkins test before, and it seems not
> > > triggering this time too.
> > >
> > > So it looks like something is broken. This might be just a HADOOP jira
> > > issue (HDFS jira seems to be fine).
> > >
> > > Thanks a lot for looking into.
> > >
> > > --Yongjun
> > >
> >
>

--089e01184810ec1d0a0507d951c9--