enricodente opened a new pull request #878:
URL: https://github.com/apache/cordova-ios/pull/878


   Updated with new self-hosted CDN instead of GitHub, due to GitHub rate 
limiting solves issue when running 'pod install'.
   
   Official reference: https://blog.cocoapods.org/CocoaPods-1.7.2/
   SO reference: 
https://stackoverflow.com/questions/23755974/cocoapods-pod-install-takes-forever
   
   ### Platforms affected
   Apple, building for iOS
   
   
   ### Motivation and Context
   Everytime 'pod install' was requested, the GitHub repository rate made the 
cloning too long. The team moved to a self-hosted CDN (which is also the main 
one now), that solves the issue with very fast cloning.
   
   
   
   ### Description
   Replaced all occurrences of 'https://github.com/CocoaPods/Specs.git' with 
'https://cdn.cocoapods.org/' (will take effect in the content of the generated 
Podfile).
   
   
   
   ### Testing
   I had to build a project that won't compile if I could not run 'pod 
install'. After the changes I could.
   
   
   
   ### Checklist
   
   - [x ] I've run the tests to see all new and existing tests pass
   - [x ] I added automated test coverage as appropriate for this change
   - [x ] Commit is prefixed with `(platform)` if this change only applies to 
one platform (e.g. `(android)`)
   - [x ] If this Pull Request resolves an issue, I linked to the issue in the 
text above (and used the correct [keyword to close issues using 
keywords](https://help.github.com/articles/closing-issues-using-keywords/))
   - [x ] I've updated the documentation if necessary
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to