> On Jun 1, 2016, at 2:49 AM, Amila Wijayarathna <[email protected]>
> wrote:
>
> Hi Chris,
>
> Thank you for replying. I extracted that file earlier and I went
> through http://yetus.apache.org/documentation/0.2.1/precommit-basic/
> <http://yetus.apache.org/documentation/0.2.1/precommit-basic/> and
> installed base requirements also. Now i need to know how to use Apache
> Yetus test-patch for the pre-commit checks.
> Any idea about this is thoroughly appreciated.
At this point, you should try running test-patch manually against your
source tree by putting together the options that are covered in the basic
guide. For example:
[*NOTE* This is the destructive form which assumes the source repo is safe to
modify! Do not use this for your "working" repo!]
YETUS_HOME/bin/test-patch \
--basedir=repo \
--patch-dir=out \
--plugins=all \
--project=myproject \
--resetrepo \
(whatever else is required) \
patchfile
When it comes time to run this under Jenkins, you should be able to
combine these options:
* command line arguments you when run manually
* --jenkins
* any other additional options you want to run specifically for automation (I
recommend running test-patch --plugins=all --help to see everything since I
don't think all of the options are fully documented. e.g., --console-urls is
handy under Jenkins)
... to create your parameterized Jenkins build job. The key parameter being how
test-patch gets the patch file information; that's obviously going to be
dependent upon your issue tracker or whatever else you'd like to use to trigger
test-patch.
[... and this goes back to something that Aldrin said in an earlier thread: we
definitely need a quickstart for the various Yetus components. I've been
thinking a lot about that over the past day or so, esp while hacking on the qbt
jobs.]
