You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by lg...@apache.org on 2018/11/22 11:54:36 UTC

[beam] 01/01: [BEAM-6011] Docs: Add a paragraph about Nexmark Phrase triggering

This is an automated email from the ASF dual-hosted git repository.

lgajowy pushed a commit to branch nexmark-docs-fix
in repository https://gitbox.apache.org/repos/asf/beam.git

commit f024c037f05a9f8f5e9fa1eb047fb69a7fcf1c4c
Author: Łukasz Gajowy <lg...@apache.org>
AuthorDate: Thu Nov 22 12:54:25 2018 +0100

    [BEAM-6011] Docs: Add a paragraph about Nexmark Phrase triggering
---
 website/src/documentation/sdks/nexmark.md | 43 +++++++++++++++++++++++++++++++
 1 file changed, 43 insertions(+)

diff --git a/website/src/documentation/sdks/nexmark.md b/website/src/documentation/sdks/nexmark.md
index 42e77c4..baefdcd 100644
--- a/website/src/documentation/sdks/nexmark.md
+++ b/website/src/documentation/sdks/nexmark.md
@@ -675,6 +675,49 @@ Submit to the cluster:
             --streaming=false \
             --manageResources=false \
             --monitorJobs=true"
+	   
+### Running Nexmark Suites on Pull Requests
+
+Thanks to ghprb plugin it is possible to run Jenkins jobs when specific phrase is typed in a Github Pull Request’s comment. Nexmark suites also can be triggered this way. You can run Nexmark suites by typing the following comments:
+
+<table class="table">
+  <thead>
+    <tr>
+     <td>
+      <strong>Runner</strong>
+     </td>
+     <td>
+       <strong>Comment</strong>
+     </td>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+     <td>Direct
+     </td>
+     <td>Run Direct Runner Nexmark Tests
+     </td>
+    </tr>
+    <tr>
+     <td>Dataflow
+     </td>
+     <td>Run Dataflow Runner Nexmark Tests
+     </td>
+    </tr>
+    <tr>
+     <td>Flink
+     </td>
+     <td>Run Flink Runner Nexmark Tests
+     </td>
+    </tr>
+    <tr>
+     <td>Spark
+     </td>
+     <td>Run Spark Runner Nexmark Tests 
+     </td>
+    </tr>
+  </tbody>
+</table>
 
 ## Nexmark dashboards
 Below dashboards are used as a CI mechanism to detect no-regression on the Beam components. They are not supposed to be benchmark comparision of the runners or engines. Especially because: