[hbase] branch master updated: HBASE-22549 Document how to re-run github PR checks

[st...@apache.org]

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

stack pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hbase.git


The following commit(s) were added to refs/heads/master by this push:
     new 4d4f4ee  HBASE-22549 Document how to re-run github PR checks
4d4f4ee is described below

commit 4d4f4ee4d11272df68d18f8205e932fcbe278401
Author: stack <st...@apache.org>
AuthorDate: Thu Jun 6 09:14:03 2019 -0700

    HBASE-22549 Document how to re-run github PR checks
    
    Signed-off-by: Peter Somogyi <ps...@cloudera.com>
---
 src/main/asciidoc/_chapters/developer.adoc | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/src/main/asciidoc/_chapters/developer.adoc b/src/main/asciidoc/_chapters/developer.adoc
index deff8da..14a549c 100644
--- a/src/main/asciidoc/_chapters/developer.adoc
+++ b/src/main/asciidoc/_chapters/developer.adoc
@@ -2387,6 +2387,28 @@ Avoid merge commits, as they create problems in the git history.
 
 See <<appendix_contributing_to_documentation,appendix contributing to documentation>>.
 
+====== How to re-trigger github Pull Request checks/re-build
+
+A Pull Request (PR) submission triggers the hbase yetus checks. The checks make
+sure the patch doesn't break the build or introduce test failures. The checks take
+around four hours to run (They are the same set run when you submit a patch via
+HBASE JIRA). When finished, they add a report to the PR as a comment. If a problem
+w/ the patch -- failed compile, checkstyle violation, or an added findbugs --
+the original author makes fixes and pushes a new patch. This re-runs the checks
+to produce a new report.
+
+Sometimes though, the patch is good but a flakey, unrelated test has the report vote -1
+on the patch. In this case, **committers** can retrigger the check run by doing a force push of the
+exact same patch. Or, click on the `Console output` link which shows toward the end
+of the report (For example `https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-289/1/console`).
+This will take you to `builds.apache.org`, to the build run that failed. See the
+"breadcrumbs" along the top (where breadcrumbs is the listing of the directories that
+gets us to this particular build page). It'll look something like
+`Jenkins > HBase-PreCommit-GitHub-PR > PR-289 > #1`. Click on the
+PR number -- i.e. PR-289 in our example -- and then, when you've arrived at the PR page,
+find the 'Build with Parameters' menu-item (along top left-hand menu). Click here and
+then `Build` leaving the JIRA_ISSUE_KEY empty. This will re-run your checks.
+
 ==== Dialog
 
 Committers should hang out in the #hbase room on irc.freenode.net for real-time discussions.