www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jake Farrell <jfarr...@apache.org>
Subject Re: Request to add RANGER as part of PreCommit-Admin job filter
Date Thu, 19 Nov 2015 21:57:26 GMT
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 <sneethir@apache.org>
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-
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message