On Mon, Jun 15, 2015 at 1:39 PM, Yongjun Zhang wrote:
> Thanks Sean and Allen!
>
> I was not aware of that there is already a way to trigger branch-2 test.
> Good to know.
>
> There are multiple solutions here:
>
> 1. When posting patches, we can post two versions of patches, one for
> trunk, and
Thanks Sean and Allen!
I was not aware of that there is already a way to trigger branch-2 test.
Good to know.
There are multiple solutions here:
1. When posting patches, we can post two versions of patches, one for
trunk, and one for branch-2, so to trigger two pre-commit jenkins test for
both b
On Jun 14, 2015, at 1:00 PM, Yongjun Zhang wrote:
> From time to time we saw changes that work fine in trunk but not branch-2,
> and we don't catch the issue in a timely manner. The difference between
> trunk and branch-2 is sufficient to justify periodic jenkins test and even
> pre-commit test
pre-commit will already test on branch-2 provided you follow the patch
naming guidelines.
there is also a branch-2 specific jenkins job:
https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-branch2/
I'd suggest starting by looking at that job and filing jiras to address
whatever the failures
Hi,
We touched this topic before but it was put on hold. I'd like to bring it
to our attention again.
>From time to time we saw changes that work fine in trunk but not branch-2,
and we don't catch the issue in a timely manner. The difference between
trunk and branch-2 is sufficient to justify per
