Merge pull request #1 from Automattic/add/cocoapods-support

Add Cocoapods support

Author: jkmassel

bin/cache_cocoapods

@@ -0,0 +1,10 @@
+#!/bin/bash
+
+set -e
+
+# Follow the typical pod installation process...
+install_cocoapods
+
+# ...then overwrite the cache for future jobs to use
+save_cache ~/.cocoapods "$BUILDKITE_PIPELINE_SLUG-specs-repos" --force
+save_cache ~/Library/Caches/CocoaPods/ "$BUILDKITE_PIPELINE_SLUG-global-pod-cache" --force

bin/cache_repo

@@ -0,0 +1,19 @@
+#!/bin/bash
+
+set -e
+
+AWS_BUCKET=$1
+
+DATE=$(date +"%Y-%m-%d")
+
+mkdir -p "/tmp/$DATE"
+
+# Download the repo
+git clone --mirror $BUILDKITE_REPO "/tmp/$DATE/$BUILDKITE_PIPELINE_SLUG.git"
+
+# Create the tarball
+TAR_NAME=$DATE.git.tar
+tar -C "/tmp/$DATE" -cvf $TAR_NAME $BUILDKITE_PIPELINE_SLUG.git
+
+# Copy the file to S3
+aws s3 cp $TAR_NAME s3://$AWS_BUCKET/$BUILDKITE_ORGANIZATION_SLUG/$BUILDKITE_PIPELINE_SLUG/$TAR_NAME

bin/install_cocoapods

@@ -0,0 +1,24 @@
+#!/bin/bash
+
+set -e
+
+# Start by restoring specs repo and pod cache:
+# - The specs repo cache holds all of the Podspec files. This avoids having download them all from the CDN.
+# - The pod cache holds the downloaded Pod source files. This avoids having to check them out again.
+restore_cache "$BUILDKITE_PIPELINE_SLUG-specs-repos"
+restore_cache "$BUILDKITE_PIPELINE_SLUG-global-pod-cache"
+
+# Restore the local `Pods` directory based on the `Podfile.lock` contents
+restore_cache "$(hash_file Podfile.lock)"
+
+# If the `pod check` plugin is installed, use it to determine whether or not to install Pods at all
+# If it's not installed (or if it fails), we'll try to install Pods. 
+# If that fails, it may be due to an out-of-date repo. We can use `--repo-update` to try to resolve this automatically.
+if [ $(bundle exec pod plugins installed | grep check) ]; then
+	bundle exec pod check || bundle exec pod install || bundle exec pod install --repo-update --verbose
+else
+	bundle exec pod install || bundle exec pod install --repo-update --verbose
+fi
+
+# If this is the first time we've seen this particular hash of `Podfile.lock`, create a cache entry for future use
+save_cache Pods "$(hash_file Podfile.lock)"

bin/install_gems

@@ -0,0 +1,12 @@
+#!/bin/bash
+
+set -e
+
+ARCHITECTURE=$(uname -m)
+CACHEKEY="$BUILDKITE_PIPELINE_SLUG-$ARCHITECTURE-ruby$(cat .ruby-version)-$(hash_file Gemfile.lock)"
+
+restore_cache $CACHEKEY
+bundle install
+
+# If this is the first time we've seen this particular cache key, save it for the future
+save_cache vendor/bundle $CACHEKEY

bin/restore_cache

@@ -6,7 +6,7 @@ CACHE_KEY=$1
 
 if [ -z "$CACHE_BUCKET_NAME" ]; then
 	echo "⛔Unable to save file to cache – no \$CACHE_BUCKET_NAME is set"
-	return 1
+	exit 0
 fi
 
 if aws s3api head-object --bucket "$CACHE_BUCKET_NAME" --key "$CACHE_KEY" > /dev/null 2>&1; then
@@ -21,5 +21,5 @@ if aws s3api head-object --bucket "$CACHE_BUCKET_NAME" --key "$CACHE_KEY" > /dev
 	echo "	Cleaning Up"
 	rm "$CACHE_KEY"
 else
-	echo "No cache entry found"
+	echo "No cache entry found for '$CACHE_KEY'"
 fi

bin/save_cache

@@ -37,6 +37,12 @@ if [ -z "$CACHE_BUCKET_NAME" ]; then
 	fi
 fi
 
+# Use with caution – in general it's not a good idea to overwrite a cache entry
+if [[ $3 == '--force' ]]; then
+	echo "Deleting the existing cache key"
+	aws s3 rm "s3://a8c-ci-cache/$CACHE_KEY"
+fi
+
 if ! aws s3api head-object --bucket "$CACHE_BUCKET_NAME" --key "$CACHE_KEY" > /dev/null 2>&1; then
 	echo "No existing cache entry for $CACHE_KEY – storing in cache"