[ 
https://issues.apache.org/jira/browse/YETUS-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255142#comment-15255142
 ] 

Sean Busbey commented on YETUS-156:
-----------------------------------

{code}
+When using an automation tool, it may be useful to use the
+`--console-report-file` option to send the summary email to a
+file. This can then be used with systems like Jenkin's
+email-ext plug-in to send the output as an emailed report:
+
{code}

worth mentioning --html-report-file here as well?

{code}
+ln -s test-patch.sh "${bin_tarball}/lib/precommit/qbt.sh"
{code}

Any advantage to using a symlink and detecting the invocation name compared to 
making the convenience wrapper pass --empty-patch when invoking test-patch.sh?

{code}
+# This bug system provides github integration
+
+add_bugsystem htmlout
{code}

I think the comment is a copy/paste error (or I need more info cause I don't 
grok how this hooks into github)

{code}
diff --git a/precommit/test-patch.d/test4tests.sh 
b/precommit/test-patch.d/test4tests.sh
index 644fbf9..6c3230c 100755
--- a/precommit/test-patch.d/test4tests.sh
+++ b/precommit/test-patch.d/test4tests.sh
@@ -27,6 +27,10 @@ function test4tests_patchfile
   declare testReferences=0
   declare i
 
+  if [[ "${BUILDMODE}" = full ]]; then
+    return
+  fi
+
{code}

the lack of any tests in the source tree seems like a big red flag, but I 
suppose this will say "everything is fine" too often to be useful? In full mode 
could it only vote when it would vote -1?

> [Umbrella] build driver
> -----------------------
>
>                 Key: YETUS-156
>                 URL: https://issues.apache.org/jira/browse/YETUS-156
>             Project: Yetus
>          Issue Type: New Feature
>          Components: Test Patch
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>         Attachments: YETUS-156.02.patch, YETUS-156.03.patch
>
>
> it might be useful to create something that runs test-patch's plug-ins as 
> part of a build process. In other words, perform a full source build, 
> generating reports from checkstyle, findbugs, shellcheck, multi-jdk, etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to