-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New SauceLabs EU Data Center #21
Comments
Thanks for notifying me. I can make these changes if you'd like. However, you could also use this as an opportunity to learn open source development. It's easy to participate!
You don't need push access to my repo to submit a Pull Request. Follow these steps:
Once you submit the Pull Request, I will either accept the Pull Request as-is, or I will request that you make changes to your branch. Once satisfied, I will merge the Pull Request (adding the commits from your branch to my repo's master branch). for more details, see: https://help.github.com/en/articles/creating-a-pull-request-from-a-fork Thanks! |
bump |
@cgoldberg my understanding is that the current implementation of apibase on master is enough for the use of EU DC. My only problem is that PyPI doesn't have a release with the relevant commit so I have to use an awkward Can you create a release in PyPI? |
Bump |
Hi there,
A few days back SauceLabs have inaugurated their new EU Data Centre in Frankfurt. In order to switch to it there are some changes that need to be performed within the sauceclient.py file like:
self.apibase = apibase or 'eu-central-1.saucelabs.com'
and
def get_job_asset_url(self, job_id, filename):
"""Get details about the static assets collected for a specific job."""
return 'https://eu-central-1.saucelabs.com/rest/v1/{}/jobs/{}/assets/{}'.format(
self.client.sauce_username, job_id, filename)
I didn't have push access to propose the update as part of a new branch / pull request thus raised it as an issue!
Please have a look at this page for the new details provided by SauceLabs here
Regards,
Ray
The text was updated successfully, but these errors were encountered: