Skip to content
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.

fix(sauce): bring back sauceProxy as a configuration option #4419

Merged
merged 1 commit into from
Aug 3, 2017

Conversation

cnishina
Copy link
Member

@cnishina cnishina commented Aug 1, 2017

Reverts the change to PR #3868. Protractor should connect to Sauce Labs
via the sauceProxy. This is different than the webDriverProxy. The
webDriverProxy is tied to the browser session where we define where the
traffic will go through.

closes #4405

@cnishina
Copy link
Member Author

cnishina commented Aug 1, 2017

@kenisteward and @heathkit could you review my comments and PR?

Copy link
Contributor

@NickTomlin NickTomlin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💃 I think this makes sense to me

@kenisteward
Copy link

kenisteward commented Aug 2, 2017 via email

@kenisteward
Copy link

kenisteward commented Aug 2, 2017 via email

Reverts the change to PR angular#3868. Protractor should connect to Sauce Labs
via the sauceProxy. This is different than the webDriverProxy. The
webDriverProxy is tied to the browser session where we define where the
traffic will go through.

closes angular#4405
@cnishina cnishina merged commit 4b7cada into angular:master Aug 3, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Proposal: Bring Back sauceProxy configuration
4 participants