Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
MIME-Version: 1.0
In-Reply-To: <61E78A26-AF3B-4816-9C21-92AB94D13228@hortonworks.com>
References: <005DC30D-DE65-41B5-B3C1-93D2D9AF000F@hortonworks.com>
 <CAAY7cL9PkxqMLNZ7R9pnnVbDcCZjZiUv1wCrqse16ToNpY0JQQ@mail.gmail.com>
 <EAB86216-4CAD-49EC-BB8E-09B19369A15F@hortonworks.com> <CAAY7cL-4xqY1VQRPsuUOHCRdCyD8Fz8nG2VLF_3ML7PCVR2HTw@mail.gmail.com>
 <61E78A26-AF3B-4816-9C21-92AB94D13228@hortonworks.com>
From: Sergio Pena <sergio.pena@cloudera.com>
Date: Wed, 19 Oct 2016 16:57:46 -0500
Message-ID: <CAAY7cL-Vwa2pHwypFPZDRqhOkvJ4iAqp9+Gi0Su1LVd0s_7gGg@mail.gmail.com>
Subject: Re: Precommit test on a feature branch
To: Wei Zheng <wzheng@hortonworks.com>
Cc: "dev@hive.apache.org" <dev@hive.apache.org>
Content-Type: multipart/alternative; boundary=001a113cdf3446686c053f3ee647
archived-at: Wed, 19 Oct 2016 21:57:53 -0000

--001a113cdf3446686c053f3ee647
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

That job is to trigger the build manually in a specific branch, but if you
attach a file to JIRA ticket, then you should look in the default job:
https://builds.apache.org/view/H-L/view/Hive/job/PreCommit-HIVE-Build/

That job will parse the patch filename, and use the branch specified.

On Wed, Oct 19, 2016 at 4:51 PM, Wei Zheng <wzheng@hortonworks.com> wrote:

> Great! Thanks! So this is where I will be looking for my Jenkins job?
>
> https://builds.apache.org/view/H-L/view/Hive/job/HIVE-Branch-Test/
>
>
>
> Thanks,
>
> Wei
>
>
>
> *From: *Sergio Pena <sergio.pena@cloudera.com>
> *Date: *Wednesday, October 19, 2016 at 14:20
> *To: *Wei Zheng <wzheng@hortonworks.com>
> *Cc: *"dev@hive.apache.org" <dev@hive.apache.org>
> *Subject: *Re: Precommit test on a feature branch
>
>
>
> Done. I added the hive-14535-mr2.properties file.
>
>
>
> You can now attach a patch like 'HIVE-XXXX-hive-14535.patch
>
>
>
> On Wed, Oct 19, 2016 at 4:06 PM, Wei Zheng <wzheng@hortonworks.com> wrote=
:
>
> Thanks Sergio. The branch we want to do test on is =E2=80=9Chive-14535=E2=
=80=9D.
> Appreciate your help!
>
>
>
>
>
> Thanks,
>
> Wei
>
>
>
> *From: *Sergio Pena <sergio.pena@cloudera.com>
> *Date: *Wednesday, October 19, 2016 at 13:15
> *To: *Wei Zheng <wzheng@hortonworks.com>
> *Cc: *"dev@hive.apache.org" <dev@hive.apache.org>
> *Subject: *Re: Precommit test on a feature branch
>
>
>
> There are 2 ways:
>
>
>
> A) Execute a jenkins job manually, and specify the branch to test (Note:
> You need Jenkins user/pass to do it):
>
> https://builds.apache.org/view/H-L/view/Hive/job/HIVE-Branch-Test/
>
>
>
> B) Create a JIRA (it can be a Task jira) where you can attach a patch tha=
t
> tells Jenkins to trigger tests in a specific branch:
>
> For instance, HIVE-XXXX-branch-1.patch    (The patch can have a small
> change enough to trigger a build)
>
>
>
> For both options, we must have a properties file on the hiveptest server
> for such specific branch.
>
> Currently, we have the following properties: branch-1.2-mr2.properties
>  branch-1-mr2.properties  branch-2.1-mr2.properties  master-mr2.propertie=
s
>  spark-mr2.properties
>
>
>
> We're working on making this easier, for for now we need to do the last
> piece manually.
>
>
>
> What branch do you want to execute? I can create the properties file on
> the server.
>
>
>
> On Wed, Oct 19, 2016 at 12:53 PM, Wei Zheng <wzheng@hortonworks.com>
> wrote:
>
> Is there a way to run precommit test against a feature branch?
>
>
>
>
>
> Thanks,
>
> Wei
>
>
>
>
>

--001a113cdf3446686c053f3ee647--