Multi-subproject patches used to work. If they don't work now, it is
probably a bug in test-patch.sh that we should fix. The code there is
written expecting multi-project changes, but maybe it doesn't get much of a
workout normally.
Conceptually, I think it's important to support patches that mo
Thanks Chris and Ray, I created
https://issues.apache.org/jira/browse/INFRA-8655 for this matter.
--Yongjun
On Tue, Nov 18, 2014 at 2:58 PM, Ray Chiang wrote:
> I had to go back and look, but it was Akira Ajisaka that had recommended it
> back when I ran into the issue:
>
>
> https://issues.a
That's an interesting find. This has not always been the case. In the
past, we've provided consolidated patches on a HADOOP jira to get
pre-commit coverage when changes span multiple sub-projects. Yongjun, if
you haven't already done so, I suggest filing a jira for this.
Chris Nauroth
Hortonwor
For all's info, confirmed what Ray stated, indeed it's the reason!
Thanks.
--Yongjun
On Fri, Nov 14, 2014 at 2:40 PM, Yongjun Zhang wrote:
> Many thanks Ray, good to know!
>
> --Yongjun
>
> On Fri, Nov 14, 2014 at 2:03 PM, Ray Chiang wrote:
>
>> Your patch covers multiple projects (I see 81
Many thanks Ray, good to know!
--Yongjun
On Fri, Nov 14, 2014 at 2:03 PM, Ray Chiang 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 th
Adding builds@apache
On Fri, Nov 14, 2014 at 1:34 PM, Yongjun Zhang 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.
>
> Than
