racker/rax-jenkins

Name: rax-jenkins

Owner: racker

Description: Fork of autoscale-chef that focuses on Jenkins

Created: 2013-04-03 21:25:01.0

Updated: 2013-12-22 00:17:49.0

Pushed: 2013-05-23 22:49:29.0

Homepage: null

Size: 441

Language: Ruby

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

rax-jenkins

Introduction

This is a fork of the autoscale-chef repo, with many large parts removed from that repo to focus on bringing up Jenkins master/slave machines.

Servers

You'll need to spin up at least two Linux (Ubuntu) servers, one to act as master and one to act as a slave to run the actual jobs. Obviously you can have more than one slave machine.

Create a local .ssh/chef.config file (NOT on the remote servers where you're going to install Jenkins) and put your servers in it. It's a good idea to separate out Chef related SSH entries from the standard ones in your .ssh/config.

Example:

Host 10.10.10.10
    user root
    IdentityFile /Users/ltorvalds/.ssh/id_rsa

Host project-foobar-jenkins-master
    user root
    IdentityFile /Users/gvanrossum/.ssh/id_rsa
    Hostname 10.10.10.10

Highly Recommended

Add an SSH public key to the root user on the remote servers, in .ssh/authorized_keys, so you do not have to continually provide a password when running the bootstrapper.

Set Up

1. You will need to create a Github racker/secure entry for the rax-jenkins folder. Follow the instructions in the README at https://github.com/racker/secure

2. Once you have access, from within the secure repo:

   $ ./handler.py -d -s rax-jenkins
   

   The data_bag_secret_key.txt will be decrypted to the rax-jenkins/ directory. Move it to some location outside of the repo on your local machine (i.e. /etc/chef/)

3. Checkout the racker/rax-jenkins repo

4. Change the bootstrap.py to reflect where you put the data_bag_secret_key.txt

5. Follow the README instructions in the nodes directory for creating node JSON files for your master and slave(s)

6. Make sure that you change roles/jenkins_master.json “proxy_hostname” to point to either the IP or FQDN of your Jenkins master. You can send an email to Felix Sargent (felix.sargent@rackspace.com) to request a rax.io subdomain be added that points to your Jenkins master's IP (i.e. teamX-jenkins.rax.io).
   

Run

Simply run ./bootstrap.py

$ ./bootstrap.py -H 10.10.10.10

or

$ ./bootstrap.py -H mywidget-jenkins-master

Jenkins Config

1. It is strongly recommended that some form of auth be put in place to secure the Jenkins master. Either htpasswd or the (public) Github OAuth plugin be used.

   a. The Github OAuth plugin is extremely easy to configure. Within your Github account, go to https://github.com/settings/applications and add your Jenkins master, following the instructions. Once created, you can maintain ownership or transfer to another organization (i.e. “racker”)

   b. On the Jenkins Master – Manage Jenkins » Configure Global Security – Under 'Access Control' choose 'Github Authentication Plugin' and fill in the appropriate fields with the information from the Githup application you just configured

2. Set the number of executors on the Jenkins master to zero – Manage Jenkins » Configure System

3. Within the Jenkins master, make sure to add the slave(s) – Manage Jenkins » Manage Nodes » New Node

   a. Make sure you set 2 - 5 executors on each slave – Click on slave link » Configure