Setup Build Slave

TBD: describe general setup and meaning of on readme.

Xcode and Various Command Line Tools

To build and test the various artifacts during the build, each slave needs a set of command line tools. If you don't setup this machine from scratch it is very likely that you already have some of them installed.

• Install Xcode Command Line Tools and/or full Xcode from MAS.
• If using full Xcode, you'll need to agree to the license by running: xcodebuild -license
• Homebrew ruby -e "$(curl -fsSL https://raw.github.com/mxcl/homebrew/go)" http://mxcl.github.com/homebrew/
• Git brew install git http://git-scm.com
• JavaScript Tools (node+npm and PhantomJS)
• Node.js brew install node http://nodejs.org (make sure npm exists)
• PhantomJS brew install phantomjs http://phantomjs.org
• ios-sim brew install ios-sim https://github.com/phonegap/ios-sim
• Android (SDK, AVD with android 17, environment variables)
  • SDK brew install android-sdk http://developer.android.com/sdk
  • Android Platform Tools, etc. android update sdk -u --filter platform-tools,android-17,system-image,extra-intel-Hardware_Accelerated_Execution_Manager
  • create and AVD android create avd -n default -t android-17 -b x86
  • if not installed via brew make sure ANDROID_SDK_ROOT is set and android and adb are on the path

SSH key pair

CloudBee's custom build slaves need to be authorized via SSH and require you to provide a public SSH key. For security reasons you should not re-use and store your personal SSH keys on a dedicated build server. Instead, create a new pair exclusively for for authenticate the build slave against CloudBees.

• ssh-keygen -t rsa -f cloudbees-slave -N ""

This commands create a pair without passphrase and stores it as cloudbees-slave(.pub) in the current directory. Please send us the public key, so we can register your node.

Start CloudBees Slave

• create new empty directory (preferrably without whitespaces in full path)
• put your private key from above into this directory and keep its name cloudbees-slave
• put jenkins-cli.jar into it
• put run-cloudbees-slave.sh into and chmod +x it
• run ./run-cloudbees-slave.sh
• (if dialog asks for installing Java, please do so and run again)

If the script terminates with "Authentication failed. No private key accepted." we haven't received your private SSH key, yet. Please wait until we registered your build slave.

Automatically Launch CloudBees Slave on Startup

TBD