Return-Path: X-Original-To: apmail-builds-archive@minotaur.apache.org Delivered-To: apmail-builds-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1C88E1833F for ; Fri, 4 Dec 2015 23:55:51 +0000 (UTC) Received: (qmail 95012 invoked by uid 500); 4 Dec 2015 23:55:50 -0000 Delivered-To: apmail-builds-archive@apache.org Received: (qmail 94916 invoked by uid 500); 4 Dec 2015 23:55:50 -0000 Mailing-List: contact builds-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: builds@apache.org Delivered-To: mailing list builds@apache.org Received: (qmail 94893 invoked by uid 99); 4 Dec 2015 23:55:50 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Dec 2015 23:55:50 +0000 Received: from [192.168.22.113] (pool-173-79-125-151.washdc.fios.verizon.net [173.79.125.151]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 9A5D81A0149; Fri, 4 Dec 2015 23:55:49 +0000 (UTC) User-Agent: Microsoft-MacOutlook/0.0.0.151008 Date: Fri, 04 Dec 2015 18:55:45 -0500 Subject: Re: Request to add RANGER as part of PreCommit-Admin job filter From: Selvamohan Neethiraj To: CC: "dev@ranger.incubator.apache.org" , "builds@apache.org" Message-ID: <9A808565-D990-402A-A734-08AE3C7182E3@apache.org> Thread-Topic: Request to add RANGER as part of PreCommit-Admin job filter References: In-Reply-To: Mime-version: 1.0 Content-type: multipart/alternative; boundary="B_3532100150_781790957" --B_3532100150_781790957 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: 7bit Jake: Thanks for looking into this PreCommit issue for Ranger team. I see that the PreCommit-Admin job is retrieving the RANGER Jiras (see: https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-Admin/230343/console - which has RANGER-765,12775765 has been processed, ignoring ) But, it NEVER kicked off Ranger PreCommit Build - 'https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-RANGER-Build/' Is there a setting that prevents the PreCommit job being kicked off automatically ? Thanks, Selva- From: Jake Farrell Reply-To: Date: Thursday, November 19, 2015 at 4:57 PM To: "builds@apache.org" Cc: "dev@ranger.incubator.apache.org" Subject: Re: Request to add RANGER as part of PreCommit-Admin job filter RANGER project has been in both filters in use by the job admin, they are: project in (HADOOP, HDFS, ZOOKEEPER, MAPREDUCE, HBASE, SQOOP, FALCON, KNOX, TAJO, SENTRY, TEZ, RANGER, PHOENIX, LENS, YETUS) AND status = "Patch Available" ORDER BY updated DESC project in (GIRAPH, HADOOP, HDFS, HIVE, MAPREDUCE, YARN, HBASE, ZOOKEEPER, SQOOP, FALCON, TAJO, SENTRY, TEZ, RANGER, PHOENIX, LENS, YETUS) AND status = "Patch Available" AND updated >= -2w ORDER BY updated DESC is patch available getting set on the tickets? can you give me an example ticket which is not showing up for these queries that you feel should be in the list -Jake On Thu, Nov 19, 2015 at 4:08 PM, Selvamohan Neethiraj wrote: Hi: PreCommit job for RANGER project is not getting kicked off (for PATCH-AVAILABLE jiras). I just found out that the filter used by PreCommit-Admin job did not have RANGER project, which was added based on the JIRA https://issues.apache.org/jira/browse/INFRA-9405 Can someone please help with setting the PreCommit-Admin job filter to include RANGER project ? Thanks, Selva- --B_3532100150_781790957--