Very good one. Btw why the emails are sent from "Hadoop QA"?
Regards, Mohammad ________________________________ From: Alejandro Abdelnur <[email protected]> To: [email protected] Sent: Tuesday, August 21, 2012 5:41 PM Subject: oozie automated test-patch jobs are up and running Short story: Upload a patch to a JIRA & mark the JIRA as 'patch available' or upload an updated patch to an already 'patch available' JIRA. This will trigger a precommit jenkins job that will test patch and post the results in the JIRA. Example: https://issues.apache.org/jira/browse/OOZIE-957 Long story: There is a Jenkins jobs (https://builds.apache.org/job/oozie-trunk-find-patches-available/) that runs every 10 mins and looks for new uploads in all JIRAs marked as 'patch available'. For each one of those JIRAs, it submits another Jenkins job (https://builds.apache.org/job/oozie-trunk-precommit-build/) parameterized with the JIRA ID that will run test-patch on the latest uploaded patch. The scripts that do all this are in trunk/bin directory. The first Jenkins job invokes 'test-patch-find-new-patch-available-jiras', the second Jenkins job invokes 'test-patch' For developers: Before uploading your patch to JIRA you can run test-patch locally. For example: $ bin/test-patch --patch=/tmp/OOZIE-1234.patch VERY IMPORTANT: test-patch will revert/reset your SVN/GIT changes and delete ALL files not under source control. So make sure you have your changes saved (you should have them in the patch you are about to test at least) Thx -- Alejandro
