CocoaPods binary cache

A plugin that helps to reduce the build time of Xcode projects which use CocoaPods by prebuilding pod frameworks and cache them in a artifactory storage. Based on gem cocoapods-remote-cache. Support cache multiple version of dependicies stored in cache, instead of cocoapods-remote-cache.

Requirements

• Ruby: >= 2.4
• CocoaPods: >= 1.5.0

Add the gem cocoapods-binary-artifactory-cache to the Gemfile of your project.

Then, run bundle install to install the added gem.

In case you're not familiar with bundler, take a look at Learn how to set it up here.

$ gem install cocoapods-binary-artifactory-cache

Check out the documentation on how it works for more information.

First of all, create a git repo that will be used as a storage of your prebuilt frameworks. Make sure this git repo is accessible via git clone and git fetch. Specify this cache repo in the following section.

2.1. Load the cocoapods-binary-artifactory-cache plugin.

Add the following line at the beginning of Podfile:

plugin "cocoapods-binary-artifactory-cache"

2.2. Configure cocoapods-binary-cache

config_cocoapods_binary_cache(
  cache_repo: {
    "default" => {
      "remote" => "https://artifactory.youlocal.net/repo-name/",
      "local" => "~/.local-cache-path"
    }
  },
  prebuild_config: "Debug"
)

For details about options to use with the config_cocoapods_binary_cache function, check out our guidelines on how to configure cocoapods-binary-cache.

2.3. Declare pods as prebuilt pods

To declare a pod as a prebuilt pod (sometimes referred to as binary pod), add the option :binary => true as follows:

pod "Alamofire", "5.2.1", :binary => true

NOTE:

• Dependencies of a prebuilt pod will be automatically treated as prebuilt pods.
  For example, if RxCocoa is declared as a prebuilt pod using the :binary => true option, then RxSwift, one of its dependencies, is also treated as a prebuilt pod.

We provided some command line interfaces (CLI):

• Fetch from cache repo, use Envirement (ARTIFACTORY_LOGIN, ARTIFACTORY_PASSWORD) to cofigure credentionals or it will be promted to user

$ bundle exec pod binary fetch

• Prebuild binary pods, use Envirement (ARTIFACTORY_LOGIN, ARTIFACTORY_PASSWORD) to cofigure credentionals, after prebuild it will be pushed automaticly

$ bundle exec pod binary prebuild

A trivial workflow when using this plugin is to fetch from cache repo, followed by a pod installation, as follows:

$ bundle exec pod binary fetch
$ bundle exec pod install

For other usages, check out the best practices docs.

We created a project to benchmark how much of the improvements we gain from this plugin. The demo project is using the following pods:

AFNetworking
SDWebImage
Alamofire
MBProgressHUD
Masonry
SwiftyJSON
SVProgressHUD
MJRefresh
CocoaLumberjack
Realm
SnapKit
Kingfisher

Below is the result we recorded:

Hardware specs of the above benchmark:

MacBook Pro (15-inch, 2018)
Mac OS 10.14.6
Processor 2.6 GHz Intel Core i7
Memory 16 GB 2400 MHz DDR4

You can also try it out on your local:

$ cd PodBinaryCacheExample
$ sh BuildBenchMark.sh

In our real project with around 15% of swift/ObjC code from vendor pods. After applying this technique, we notice a reduction of around 10% in build time.

• When exporting an IPA with Bitcode, remember to disable the rebuild from bitcode option. Refer to grab#24.

• By default, pods with empty sources (ie. pods with header files only) will be automatically excluded and they will be later integrated as normal. For now, we rely on the source_files patterns declared in podspec to heuristically detect empty-sources pods.
• However, there are cases in which the source_files of a pod looks like non-empty sources (ex. s.source_files = "**/*.{c,h,m,mm,cpp}") despite having header files only. For those cases, you need to manually add them to the excluded_pods option.

Check out our Best practices for for information.

Check out our Troubleshooting guidelines for more information.

Check out CONTRIBUTING.md for more information on hw to contribute to this repo.

The cocoapods-binary-cache plugin is available as open-source under the terms of the MIT License. It uses cocoapods-rome and cocoapods-binary internally, which are also under MIT License.