My Xcode cloud build have been failing for some time due to failure to install brew for cocoapods. (my only dependency here is cocoa pods)
I followed the instruction in the documentation here
And have a simple ci_post_clone script here
#!/bin/sh
brew install cocoapods
pod install
The error are typically in the brew install part and often refer to a HTTP 500 error, an example pasted below, but they are not always consistent and happening at different random place in the brew update.
What should I add to my ci script to make brew and cocoapods work?
Example of error (never exactly the same)
Initialized empty Git repository in /Users/local/Homebrew/.git/
Updating Homebrew...
error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
fatal: expected flush after ref listing
==> Tapping homebrew/core
Cloning into '/Users/local/Homebrew/Library/Taps/homebrew/homebrew-core'...
error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
fatal: error reading section header 'shallow-info'
Error: Failure while executing; `git clone https://github.com/Homebrew/homebrew-core /Users/local/Homebrew/Library/Taps/homebrew/homebrew-core --origin=origin --template=` exited with 128.
Error: Failure while executing; `/Users/local/Homebrew/bin/brew tap homebrew/core` exited with 1.
/Volumes/workspace/repository/ci_scripts/ci_post_clone.sh: line 5: pod: command not found
Opened a bug report FB9929569
Similar issue using Carthage. I do not see an attempt to even install brew: ''' source /Volumes/Task/ci_build.env && source /Volumes/Task/ci_plan.env && cd /Volumes/workspace/repository/ci_scripts && bash /Volumes/workspace/repository/ci_scripts/ci_post_clone.sh
/Volumes/workspace/repository/ci_scripts/ci_post_clone.sh: line 7: brew: command not found
./build_framework.sh: line 22: carthage: command not found '''
This is new in the last few days. Prior to this I had no issues with this ci script downloading and installing homebrew and carthage.
Please open a new bug report with Apple and reference FB9929569, this is the best way to gain traction with Apple.
Also, you should be commenting on the original topic, not answering, as your answers are merely the same issue repeated again. :)