Hi all, I wanted to let you know about some changes to the PreCommit Job that I recently made.
Previously, Oozie was using https://builds.apache.org/job/oozie-trunk-find- patches-available/ to run https://github.com/apache/ oozie/blob/master/bin/test-patch-find-new-patch-available-jiras every 10 minutes. This looked for new OOZIE patches on JIRA and kicked off https://builds.apache.org/job/oozie-trunk-precommit-build/, which ran a number of other scripts to run unit tests, findbugs, etc and then post the results to the JIRA. Unfortunately, we had to tie the oozie-trunk-find-patches-available job to a specific Jenkins node because it stored a file so we don't get duplicates. This meant that (a) if that node was busy, oozie-trunk-find-patches-available would get delayed and (b) if that node was down, nothing would get run. For instance, that node has been down for about a week (https://issues.apache.org/jira/browse/INFRA-15033) and so the job hadn't been running. Hadoop, and a number of other projects, use a different mechanism which doesn't have this problem. I won't go into the details here (see https://issues.apache.org/jira/browse/OOZIE-3051), but https://builds. apache.org/job/PreCommit-Admin/ works similarly to the oozie-trunk-find-patches-available job and I've created a new https://builds.apache.org/job/PreCommit-OOZIE-Build/ job that is similar to our old oozie-trunk-precommit-build job. The old jobs have been disabled for now. Everything seems to be working now, but let me know if we run into any issues. thanks - Robert
