[ 
https://issues.apache.org/jira/browse/OOZIE-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16172035#comment-16172035
 ] 

Robert Kanter commented on OOZIE-3051:
--------------------------------------

Just some useful info to summarize how things work now:
- https://builds.apache.org/job/PreCommit-Admin runs every 10 minutes and looks 
for new patches to run on various projects (including Oozie now)
-- If you have a JIRA with "Patch Available" with an attachment that hasn't 
been run before, it will trigger
- That kicks off https://builds.apache.org/job/PreCommit-OOZIE-Build/ which 
runs the tests and other stuff, pretty much what we had before; and will post 
on the JIRA once it finishes
-- You can manually kick off a run by either reattaching the patch to the JIRA 
and waiting up to 10 minutes, or if you have Jenkins access, you can enter the 
JIRA number here: https://builds.apache.org/job/PreCommit-OOZIE-Build/build

> Replace Oozie's custom precommit build patch finding job with the standard 
> Apache one
> -------------------------------------------------------------------------------------
>
>                 Key: OOZIE-3051
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3051
>             Project: Oozie
>          Issue Type: Test
>          Components: tests
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>         Attachments: OOZIE-3051.001.patch
>
>
> We currently use a custom script in the 
> [oozie-trunk-find-patches-available|https://builds.apache.org/job/oozie-trunk-find-patches-available/]
>  Jenkins job to find patches on JIRA and submit a build to the 
> [oozie-trunk-precommit-build|https://builds.apache.org/job/oozie-trunk-precommit-build/]
>  job.  
> There's a number of downsides to this, the main one being that we need to tie 
> oozie-trunk-find-patches-available to a specific Jenkins host so we can store 
> a file to remember what JIRAs were looked at already (H1).  Unfortunately, 
> this means that whenever H1 is down, we can't get automatic pre-commit jobs.
> Many projects, including Hadoop, Pig, Hive, etc use the 
> [PreCommit-Admin|https://builds.apache.org/job/PreCommit-Admin/] job.  We 
> should do that as well.
> More details (though it appears to be a little out of date) are at 
> http://wiki.apache.org/general/PreCommitBuilds



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to