You can clone with
HTTPS or Subversion.
It appears that 0.32.0 now has absolute paths for development pods, which is breaking our CI build as well as other developer builds when pulling down the latest.
Wanted to get this up now. Will follow up with more information as I have it.
Previously, development pods were installed with a relative path:
Now, they have an absolute path:
Looking through the changelog, I see #1042
Will take a look and make sure we are doing this correctly.
This is a feature so... deal with it! No kidding you can easily fix your CI by specifying the paths as relative in your Podfile.
Hmm, this sounds somewhat related to my fix for CocoaPods/Xcodeproj#118
CocoaPods/Xcodeproj@46a66dc Just I just remembered I did this commit and have't got merged yet
Still investigating, but I updated my path to be:
:path => './ThirdPartyCode/UrbanAirship'
And re ran pod install, and it still is coming up with an absolute path.
Our original path in our podfile that broke CI was :path => 'ThirdPartyCode/UrbanAirship', which also looks like a relative path.
:path => 'ThirdPartyCode/UrbanAirship'
@irrationalfab can you verify our comments above? Are we missing something, or is there a bug here?
Can you post the Podfile?
I have removed the min version requirement from the specs repo for the time being so you can downgrade
[ExternalSources::PathSource] Fix relative path detection
Saw you just closed this. Do you still need the pod file?
No, it should be fixed.. thanks!
Can you try with CocoaPods 0.32.1?
Perfect. Thanks for the update!