From ab38246bdc041490d1b8accc43e6065a3c96166c Mon Sep 17 00:00:00 2001 From: Diana Suvorova Date: Mon, 2 Apr 2018 11:09:17 -0700 Subject: [PATCH] docs: updating links to sources --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index dfb5181..d1a6d30 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ You're a member of a popular open source project that involves front-end Web tec Specifically, the project involves JavaScript. Because it's a serious project, you have automated cross-browser testing for your JavaScript. You happen to use [Open Sauce](https://saucelabs.com/opensauce) for this. -Unfortunately, [due to certain limitations](http://support.saucelabs.com/entries/25614798-How-can-we-set-up-an-open-source-account-that-runs-tests-on-people-s-pull-requests-), it's not possible to do cross-browser testing on pull requests "the obvious way" via Travis CI without potentially compromising your Sauce login credentials. This means that either (a) cross-browser problems aren't discovered in pull requests until after they've already been merged (b) repo collaborators must manually initiate the cross-browser tests on pull requests (and manage the resulting branches, and possibly post comments communicating the test results). +Unfortunately, it's not possible to do cross-browser testing on pull requests "the obvious way" via Travis CI without potentially compromising your Sauce login credentials. Travis's JWT plugin was a [recommended solution](https://docs.travis-ci.com/user/sauce-connect/) for some time, but [it was deprecated as of April 17](https://blog.travis-ci.com/2018-01-23-jwt-addon-is-deprecated). This means that either (a) cross-browser problems aren't discovered in pull requests until after they've already been merged (b) repo collaborators must manually initiate the cross-browser tests on pull requests (and manage the resulting branches, and possibly post comments communicating the test results). By automating the process of initiating Travis-based Sauce tests and posting the results, cross-browser JavaScript issues can be discovered more quickly and with less work on the part of repo collaborators.