Page History

...

You need to set the title which starts with the corresponding JIRA issue number. (e.g. HADOOP-XXXXX. Fix a typo in YYY.)  Jenkins precommit job will search the corresponding GitHub pull request and apply the diff automatically.  If there is a corresponding pull request, you don't need to attach a patch in this issue because the precommit job always runs on pull request instead of the attached patch.  

If there is no corresponding issue, please create a issue in ASF JIRA before creating a pull request.  , or comment the patch URL (https://github.com/apache/hadoop/pull/XXX.patch) to the JIRA issue. This is because Jenkins precommit job will search the URL that starts with "https://github.com" and ends with ".patch" in the JIRA issue.

Testing your patch

Before submitting your patch, you are encouraged to run the same tools that the automated Jenkins patch test system will run on your patch. This enables you to fix problems with your patch before you submit it. The dev-support/bin/test-patch script in the trunk directory will run your patch through the same checks that Jenkins currently does except for executing the unit tests. (See TestPatchTips for some tricks.)  

...