Repository: spark-website Updated Branches: refs/heads/asf-site efcfd7fc8 -> 6ff5039f3
Describe AppVeyor CI build in "Pull Request" of controbuting guide Project: http://git-wip-us.apache.org/repos/asf/spark-website/repo Commit: http://git-wip-us.apache.org/repos/asf/spark-website/commit/6ff5039f Tree: http://git-wip-us.apache.org/repos/asf/spark-website/tree/6ff5039f Diff: http://git-wip-us.apache.org/repos/asf/spark-website/diff/6ff5039f Branch: refs/heads/asf-site Commit: 6ff5039f378f36c016e94c77889ebe331b52b3e4 Parents: efcfd7f Author: hyukjinkwon <[email protected]> Authored: Tue Jul 25 13:44:04 2017 +0900 Committer: Sean Owen <[email protected]> Committed: Tue Jul 25 09:36:51 2017 +0100 ---------------------------------------------------------------------- contributing.md | 8 ++++++-- site/contributing.html | 8 ++++++-- 2 files changed, 12 insertions(+), 4 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/spark-website/blob/6ff5039f/contributing.md ---------------------------------------------------------------------- diff --git a/contributing.md b/contributing.md index b330962..85fa478 100644 --- a/contributing.md +++ b/contributing.md @@ -295,8 +295,12 @@ with a link to the full results on Jenkins. 1. Fixes can simply be pushed to the same branch from which you opened your pull request 1. Jenkins will automatically re-test when new commits are pushed 1. If the tests failed for reasons unrelated to the change (e.g. Jenkins outage), then a - committer can request a re-test with "Jenkins, retest this please". - Ask if you need a test restarted. + committer can request a re-test with "Jenkins, retest this please". + Ask if you need a test restarted. If you were added by "Jenkins, add to whitelist" from a + committer before, you can also request the re-test. +1. If there is a change related to SparkR in your pull request, AppVeyor will be triggered +automatically to test SparkR on Windows, which takes roughly an hour. Similarly to the steps +above, fix failures and push new commits which will request the re-test in AppVeyor. <h3>The Review Process</h3> http://git-wip-us.apache.org/repos/asf/spark-website/blob/6ff5039f/site/contributing.html ---------------------------------------------------------------------- diff --git a/site/contributing.html b/site/contributing.html index 82b4431..1e2a577 100644 --- a/site/contributing.html +++ b/site/contributing.html @@ -526,10 +526,14 @@ with a link to the full results on Jenkins.</li> <li>Fixes can simply be pushed to the same branch from which you opened your pull request</li> <li>Jenkins will automatically re-test when new commits are pushed</li> <li>If the tests failed for reasons unrelated to the change (e.g. Jenkins outage), then a - committer can request a re-test with “Jenkins, retest this please”. - Ask if you need a test restarted.</li> + committer can request a re-test with “Jenkins, retest this please”. + Ask if you need a test restarted. If you were added by “Jenkins, add to whitelist” from a + committer before, you can also request the re-test.</li> </ol> </li> + <li>If there is a change related to SparkR in your pull request, AppVeyor will be triggered +automatically to test SparkR on Windows, which takes roughly an hour. Similarly to the steps +above, fix failures and push new commits which will request the re-test in AppVeyor.</li> </ol> <h3>The Review Process</h3> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
