Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 938AF17659 for ; Fri, 30 Jan 2015 06:43:28 +0000 (UTC) Received: (qmail 84887 invoked by uid 500); 30 Jan 2015 06:43:28 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 84799 invoked by uid 500); 30 Jan 2015 06:43:28 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 84785 invoked by uid 99); 30 Jan 2015 06:43:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Jan 2015 06:43:27 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ramkrishna.s.vasudevan@gmail.com designates 209.85.213.172 as permitted sender) Received: from [209.85.213.172] (HELO mail-ig0-f172.google.com) (209.85.213.172) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Jan 2015 06:43:02 +0000 Received: by mail-ig0-f172.google.com with SMTP id l13so1127927iga.5 for ; Thu, 29 Jan 2015 22:42:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=qdt5B7EKJ2RBCGjFuSQqC6xDbCbWoc8ZymNtXNrkmWM=; b=kT4ZgqSVs2XEYYgJPLsu6HE7qfzZ84p39lxaraNBcRhc1ivYcH9RKd9NzC5cZ2jd3V +GINFiVb8BcuyJy8CcsxRqN7s3fLdZNweD+TnNLtr8Mer+fMgx2QWIFvJtmW2fi76tYc AmTLxurgHHbZf5r5T1yd/JPLOCq6/OEorMp+4YT03N/4OH3aUWjAuG5Pzf0kMAsE0Eia 9032CQhi9lOfXbgfT+G3gPgEY1lUDI0QLCej+mfz208bpWdIYu0BXkffQgHlkGD5fZC4 7iHGfR+vh9xHo6jv2wI3Cw8BUcV5QdaFwk8YydQAhGqTDXgiuVXEujfwt3uEi9a1+zYE JivQ== MIME-Version: 1.0 X-Received: by 10.50.43.138 with SMTP id w10mr941837igl.19.1422600135445; Thu, 29 Jan 2015 22:42:15 -0800 (PST) Received: by 10.107.47.158 with HTTP; Thu, 29 Jan 2015 22:42:15 -0800 (PST) In-Reply-To: <709945410.2845229.1422599817274.JavaMail.yahoo@mail.yahoo.com> References: <709945410.2845229.1422599817274.JavaMail.yahoo@mail.yahoo.com> Date: Fri, 30 Jan 2015 12:12:15 +0530 Message-ID: Subject: Re: Precommit build (hadoopqa) can now test the patch on branches From: ramkrishna vasudevan To: "dev@hbase.apache.org" , lars hofhansl Content-Type: multipart/alternative; boundary=089e01176c7fbb11a6050dd8e790 X-Virus-Checked: Checked by ClamAV on apache.org --089e01176c7fbb11a6050dd8e790 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Nice feature !! On Fri, Jan 30, 2015 at 12:06 PM, lars hofhansl wrote: > This is absolutely awesome. Thanks Enis! > From: Enis S=C3=B6ztutar > To: "dev@hbase.apache.org" > Sent: Thursday, January 29, 2015 10:31 PM > Subject: Precommit build (hadoopqa) can now test the patch on branches > > Devs, > > Over at HBASE-12944, we've made some changes so that the Precommit jenkin= s > build (commonly known and loved as hadoopqa) can now test patches on > branches. > > For testing a patch on a branch, you should use the name of the branch in > name of the patch file. For example a patch file named > "hbase-123-0.98.patch will test the hadoopqa build on top of the 0.98 > branch. > > Right now, all active branches, master, branch-1.0, branch-1, 0.98 and 0.= 94 > are supported. If no branch name is found in the patch file, master will = be > used. > > Also keep in mind that hadoopqa only picks up the latest patch from an > issue in "Patch Available" state. This means that you cannot attach 3 > patches at the same time for different branches and expect hadoopqa to > report on all 3. The way to test a patch for master and branch-1 for > example would be to attach the master patch, wait for the precommit build > [1] to start for your patch, and then after it started attach the branch-= 1 > patch with "branch-1" in the patch file name. There is another job called > PreCommit-Admin [2] who looks at the jira issues and kicks the precommit > build every 10 minutes. It means you have to wait at least 10 minutes in > between (or kick [2] manually if you are a committer). > > [1] https://builds.apache.org/job/PreCommit-HBASE-Build/ > [2] https://builds.apache.org/view/All/job/PreCommit-Admin/ > > Cheers, > Enis > > > > --089e01176c7fbb11a6050dd8e790--