hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Hadoop Wiki] Update of "TestPatchTips" by SomeOtherAccount
Date Thu, 21 Jan 2016 20:40:53 GMT
Dear Wiki user,

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

The "TestPatchTips" page has been changed by SomeOtherAccount:
https://wiki.apache.org/hadoop/TestPatchTips?action=diff&rev1=3&rev2=4

Comment:
Update for Yetus

  === Introduction ===
- In the Hadoop source tree is {{{dev-support/test-patch.sh}}}.  This script used by the Jenkins
servers to run the automated QA tests.  It is possible and highly recommended to run this
script locally prior to uploading a patch to JIRA.
+ In the Hadoop source tree is {{{dev-support/bin/test-patch}}}.  This is a wrapper to invoke
[[Apache Yetus|https://yetus.apache.org]]. It is possible and highly recommended to run this
script locally prior to uploading a patch to JIRA.  Beyond just these tips, be sure to checkout
the Yetus documentation.
  
  In order to get the full power of the tool set, you'll want to make sure that both {{{findbugs}}}
and {{{shellcheck}}} are installed.
  
@@ -17, +17 @@

  Apply and run just the basic checks in a checkout that has other stuff in it:
  
  {{{
- $ dev-support/test-patch.sh --dirty-workspace /tmp/patchfile
+ $ dev-support/bin/test-patch --dirty-workspace /tmp/patchfile
  }}}
  Apply and run the full unit test:
  
  {{{
- $ dev-support/test-patch.sh --dirty-workspace --run-tests /tmp/patchfile
+ $ dev-support/bin/test-patch --dirty-workspace --run-tests /tmp/patchfile
  }}}
  Download a patch from a JIRA and run just the basic checks in a checkout that can be destroyed:
  
  {{{
- $ dev-support/test-patch.sh --resetrepo HADOOP-11820
+ $ dev-support/bin/test-patch --resetrepo HADOOP-11820
  }}}
- 
  '''Recommended Usage'''
  
  In general, the easiest way to use {{{test-patch.sh}}} is to use two repos.  One repo is
used to build patches.  The other repo is used to to test them.
@@ -37, +36 @@

  {{{
  $ git diff --no-prefix trunk > /tmp/1.patch
  
- $ dev-support/test-patch.sh --resetrepo --run-tests --basedir=/test/repo /tmp/1.patch
+ $ dev-support/bin/test-patch --resetrepo --run-tests --basedir=/test/repo /tmp/1.patch
  }}}
  This will run the freshly built patch against the tests in a fresh repo.
  

Mime
View raw message