You can clone with
HTTPS or Subversion.
This isn't really a issue, but more of a question.
I am wondering what the best practice is for getting a release build that isn't linked with PonyDebugger. Ideally, I would like to keep the release build the same as before integrating with PonyDebugger. Is there a good way to do this?
Take a look at the sample PDTwitterTest application. Basically, add -lSocketRocket and -lPonyDebugger to your Other Linker Flags for Debug builds, and get rid of them in your main Linked Frameworks and Libraries list. Then you will want to surround any PonyDebugger related code (including the #include <PonyDebugger/PonyDebugger.h) in #if DEBUG statements.
If you are using continious integration server for release builds (jenkins in my case), good option would be using cocoapods and add condition to your Podfile, so PonyDebugger isn't installed on build server. For examle:
pod 'PonyDebugger', '0.0.1'
And of course you still need to surround all PonyDebugger related code with #if DEBUG ... #endif statements.
Then just check in jenkins build log that ponydebugger isn't installed during pod install.
#if DEBUG ... #endif