Skip to content
HBehrens edited this page Feb 20, 2013 · 24 revisions

powered by CloudBees

TBD: describe general setup and meaning of Build Status on readme.

Xcode

tested on 4.5.2 and 4.6 available on MAS https://itunes.apple.com/de/app/xcode/id497799835?l=en&mt=12 Download and run once to accept EULA and install updates (no comment).

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.

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 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

Clone this wiki locally