This has little to do with you and me, and neither is CircleCI a big problem. The major problem is that CocoaPods is running a centralized system (meaning all the relevant information is in one place) off of a system they do not control (Github). Their specs repo outgrew Githubs capabilities (mostly bandwidth) and is not at almost 900 mb. So every time one of our customers is querying this repo they are downloading 900 mb. We have a lot of customers who use CocoaPods and we’re still a drop on a hot stone compared to the fact that they have close to half a million users. That means that the repo is hit roughly 10 times a second. That kind traffic is no longer maintainable by Github since the CocoaPods system is rather abusing Githubs open and free platform at this point than using it.
Githubs response to that is simply rate limit the traffic. All the bits are still flowing to everyone but it flows really really slowly. This way Github doesn’t compromise it’s open platform but can assure that other Git repos are impacted by the CocoaPods repo.
As you can see now, your build times aren’t related to your setup as in “the way we use CircleCI” and rather related to the fact that you use CocoaPods. I would suggest you either start caching the specs repo like so in your
this might introduce other issues though (its the best solution for moving forward with CocoaPods). Another possibility you have is switching to a different system. I personally really like Git LFS. It works natively with your current setup, since you already use Git, and does not make you change the way you work create a Xcode workspace and forces you to use that going forward.