[Hadoop Wiki] Update of "HowToContribute" by SomeOtherAccount

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The "HowToContribute" page has been changed by SomeOtherAccount:
https://wiki.apache.org/hadoop/HowToContribute?action=diff&rev1=113&rev2=114

Comment:
Update for Yetus

  NOTE: Our Jenkins configuration uses [[https://yetus.apache.org|Apache Yetus]].  More advanced patch file names are documented on their [[https://yetus.apache.org/documentation/in-progress/precommit-patchnames/|patch names page]].
  
  === 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/test-patch.sh}}} script in the trunk directory will run your patch through the same checks that Jenkins currently does ''except'' for executing the unit tests.
+ 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.)
  
  Run this command from a clean workspace (ie {{{git status}}} shows no modifications or additions) as follows:
  
  {{{
- dev-support/test-patch.sh [options] patch-file | defect-number
+ dev-support/bin/test-patch [options] patch-file | defect-number
  }}}
  
  At the end, you should get a message on your console that is similar to the comment added to Jira by Jenkins's automated patch test system, listing +1 and -1 results. Generally you should expect a +1 overall in order to have your patch committed; exceptions will be made for false positives that are unrelated to your patch.  The scratch directory (which defaults to the value of {{{${user.home}/tmp}}}) will contain some output files that will be useful in determining cause if issues were found in the patch.