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=112&rev2=113 Patches for a non-trunk branch should be named '''<jiraName>-<branchName>.<versionNum>.patch''', e.g. HDFS-1234-branch-2.003.patch. The branch name suffix should be the exact name of a git branch, such as "branch-2". Jenkins will check the name of the patch and detect the appropriate branch for testing. - Please note that the Jenkins pre-commit build is not run against minor branches (e.g. branch-2.7) or the branches starting with branch-0 (e.g. branch-0.23). + Please note that the Jenkins precommit build will not run against branches that use ant. It's also OK to upload a new patch to Jira with the same name as an existing patch. If you select the "Activity>All" tab then the different versions are linked in the comment stream, providing context. However, many reviewers find it helpful to include a version number in the patch name (three-digit version number is recommended), '''so including a version number is the preferred style'''. + + 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.
