beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [beam-site] 01/01: Prepare repository for deployment.
Date Thu, 06 Jul 2017 17:32:49 GMT
This is an automated email from the ASF dual-hosted git repository.

mergebot-role pushed a commit to branch asf-site
in repository

commit b4114387d3cf1633ebcbe3dba3a87cb42ceb38db
Author: Mergebot <>
AuthorDate: Thu Jul 6 17:32:46 2017 +0000

    Prepare repository for deployment.
 content/contribute/testing/index.html | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/content/contribute/testing/index.html b/content/contribute/testing/index.html
index 8e7cec1..30db095 100644
--- a/content/contribute/testing/index.html
+++ b/content/contribute/testing/index.html
@@ -412,8 +412,7 @@ precommit and postcommit testing.</p>
 <h3 id="precommit">Precommit</h3>
 <p>For precommit testing, Beam uses
-<a href="">Jenkins</a>,
-<a href="">Travis</a>, and a code coverage tool
+<a href="">Jenkins</a> and a code coverage
 called <a href="">Coveralls</a>, hooked
 to <a href="">Github</a>, to ensure that pull
 requests meet a certain quality bar. These precommits verify correctness via two
@@ -427,10 +426,9 @@ that this hits the appropriate tradeoff between a desire for short (ideally
 function in the way in which they are intended.</p>
 <p>Precommit tests are kicked off when a user makes a Pull Request against the
-<code class="highlighter-rouge">apache/beam</code> repository and the Travis,
Jenkins, and Coveralls statuses
-are displayed at the bottom of the pull request page. Clicking on “Details” will
-open the status page in the selected tool; there, test status and output can be
+<code class="highlighter-rouge">apache/beam</code> repository and the Jenkins
and Coveralls statuses are displayed at
+the bottom of the pull request page. Clicking on “Details” will open the status
+page in the selected tool; there, test status and output can be viewed.</p>
 <h3 id="postcommit">Postcommit</h3>

To stop receiving notification emails like this one, please contact
"" <>.

View raw message