Skip to content
Browse files
[FIXED JENKINS-22250] Added help file to clarify usafe of this feature
  • Loading branch information
kinow committed Aug 26, 2016
1 parent 4c04a0c commit 1c2cc09213aa590503fdb45060fe9e6598f6e353
Showing with 8 additions and 2 deletions.
  1. +2 −2 src/main/resources/org/tap4j/plugin/TapPublisher/config.jelly
  2. +6 −0 src/main/webapp/help/TapPublisher/help-failIfNoResults.html
@@ -7,8 +7,8 @@
<f:checkbox name="TapPublisher.verbose" value="${instance.verbose}" checked="${instance.verbose}" default="true" />
<f:entry title="Fail the build if no test results are present">
<f:checkbox name="TapPublisher.failIfNoResults" value="${instance.failIfNoResults}" checked="${instance.failIfNoResults}" />
<f:entry title="Fail the build if no test results (files) are found" help="/plugin/tap/help/TapPublisher/help-failIfNoResults.html">
<f:checkbox name="TapPublisher.failIfNoResults" value="${instance.failIfNoResults}" checked="${instance.failIfNoResults}"/>
<f:entry title="Failed tests mark build as failure">
<f:checkbox name="TapPublisher.failedTestsMarkBuildAsFailure" value="${instance.failedTestsMarkBuildAsFailure}" checked="${instance.failedTestsMarkBuildAsFailure}" />
@@ -0,0 +1,6 @@
This option fails the build when no test results (files) are found. So if your job is
configured to look for *.tap files, but when the plug-in looks at the workspace it
cannot find any .tap file, and this option is checked, then your build will be marked
as failure. If you have empty .tap, they still count, and the plug-in will not fail the build.

0 comments on commit 1c2cc09

Please sign in to comment.