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

Switch default binary-baseurls to s3 #4806

Merged
merged 2 commits into from Aug 9, 2017

Conversation

Projects
None yet
4 participants
@stuhood
Copy link
Member

stuhood commented Aug 9, 2017

Problem

bintray had already been performing spottily, and recently began rate limiting us.

Solution

Now that all artifacts have been migrated to s3 (and all repositories that used to push to bintray have been updated) switch the default baseurls to s3.

Result

@jsirois did a ton of other work to fix this, but as far as I can tell, this finalizes the switch. Fixes #4800.

@stuhood stuhood requested review from jsirois , benjyw and kwlzn Aug 9, 2017

@kwlzn

kwlzn approved these changes Aug 9, 2017

Copy link
Member

kwlzn left a comment

lgtm

@jsirois

jsirois approved these changes Aug 9, 2017

@baroquebobcat
Copy link
Contributor

baroquebobcat left a comment

lgtm!

@stuhood stuhood merged commit bd8f49a into pantsbuild:master Aug 9, 2017

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

@stuhood stuhood deleted the twitter:stuhood/switch-to-s3-by-default branch Aug 9, 2017

@stuhood stuhood added this to the 1.3.1 milestone Nov 3, 2017

stuhood added a commit that referenced this pull request Nov 3, 2017

Switch default binary-baseurls to s3 (#4806)
### Problem

bintray had already been performing spottily, and recently began rate limiting us.

### Solution

Now that all artifacts have been migrated to s3 (and all repositories that used to push to bintray have been updated) switch the default baseurls to s3.

### Result

@jsirois did a ton of other work to fix this, but as far as I can tell, this finalizes the switch. Fixes #4800.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment