Hi Mike, Thanks for your interest in helping Oozie work better with Bigtop. The Oozie docs has a page on Building Oozie. It mentions various maven commands and the mkdistro.sh script. It's targeted more towards end users rather than developers, but it should basically be the same info. I don't think that page has been updated in a while, so if you see anything that needs to be updated there, please file a JIRA. http://archive.cloudera.com/cdh5/cdh/5/oozie/ENG_Building.html
I can't speak for other developers, but personally, I typically just run the relevant tests before uploading the patch to JIRA. Our test-patch script isn't nearly as fancy as Hadoop's, and it runs all tests, which can take 1-2 hours. So running the relevant tests locally as a sanity check and letting Jenkins run all of the tests is usually the best strategy for me. Unfortunately, our Jenkins job has been having problems lately (jvm exists for some reason), and we haven't been able to fix it just yet. And if you have anything useful to add or improve on our wiki, please do so. thanks - Robert On Mon, Nov 9, 2015 at 11:53 AM, Mike Grimes <[email protected]> wrote: > Hi, > > I’m interested in committing some work back to Oozie that I’ve done to get > it working well with Bigtop. I’ve searched a bit on the email archives but > haven’t found too much discussion around guides for new developers. I’m > mostly looking for a guide or set of community guidelines on how to build > Oozie (do I just use the standard mkdistro.sh script in bin?) and how to > test patches locally before submitting to a JIRA, to lower the amount of > overhead required by members of the community. Does documentation like this > exist? I’d be interested in helping create some if the information is > spread out among archived emails, or other documents. > > Right now I’m mostly concerned with testing my work before submitting a > patch. On > https://cwiki.apache.org/confluence/display/OOZIE/How+To+Contribute there > isn’t any mention of running ./bin/test-patch locally before submitting a > patch on a JIRA. Is this supported, and a recommended workflow? > > Best, >
