Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of rchiang@cloudera.com designates
 209.85.220.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALte62whJ36FgqLb4qhoHKZkcX2umbpQ6+S=xrkoTk8ZOU2JQw@mail.gmail.com>
References: 
 <CAA0W1bRW0StVC7+Lrz+KUL5j0iQW5NgbjiJFEw4BvGB26kWc8A@mail.gmail.com>
	<CALte62whJ36FgqLb4qhoHKZkcX2umbpQ6+S=xrkoTk8ZOU2JQw@mail.gmail.com>
Date: Fri, 14 Nov 2014 14:03:15 -0800
Message-ID: 
 <CADPoNvyND+KuYrEmW2m3RJ3EZHLiojT+i1_NADN7WV76=vdegA@mail.gmail.com>
Subject: Re: submitting a hadoop patch doesn't trigger jenkins test run
From: Ray Chiang <rchiang@cloudera.com>
To: common-dev@hadoop.apache.org
Cc: "builds@apache.org" <builds@apache.org>
Content-Type: multipart/alternative; boundary=20cf307ca414bca82c0507d8cb83

--20cf307ca414bca82c0507d8cb83
Content-Type: text/plain; charset=UTF-8

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
> >
>

--20cf307ca414bca82c0507d8cb83--