And by jar I mean patch. On 17/8/15, 12:56, "Sergey Shelukhin" <ser...@hortonworks.com> wrote:
>Specifying the branch name as part of the jar is the trigger. I’ve never >tried it for more than one branch at a time so I’m not sure if HiveQA >would run for every one; it seems more likely that it would pick the >latest patch, whatever that happens to be. >Also, for that to actually work the branches have to be added to some >ptest config that ptest admins can do. I think only the main branches >(e.g. branch-1/2) are set up by default. > >On 17/8/15, 12:54, "Mithun RK" <mythro...@gmail.com> wrote: > >>Hello, hive-dev. >> >>I was wondering if anyone could clarify how to get pre-commit tests to >>run >>for branches other than master. >> >>The dev documentation >><https://cwiki.apache.org/confluence/display/Hive/HowToContribute#HowToCo >>n >>tribute-CreatingaPatch> >>indicates >>that if the branch-name is specified as per the naming convention, >>pre-commit tests should run on the appropriate branch. It doesn't mention >>anything about setting target-versions, etc. I only seem to have had >>tests >>run on master. >> >>Does one have to cancel-patch + submit-patch for every branch? That >>sounds >>unwieldy. >> >>Regards, etc. >>Mithun >
