So, we have Jenkins up and running, we just need to add a few packages.

pkgin in gmake gcc47

This will install the compilers and make tools to get started.

If you would like to work with ruby, try:

pkgin in ruby193
gem update --system

Jenkins can also have manage and run jobs on multiple nodes. This is nice when you have a busy group of developers, or long running jobs.

You’ll need another virtual machine to act as a slave.

{
	"brand": "joyent", 
	"alias": "jenkins-slave", 
	"zonename": "jenkins-slave",
	"domain": "local",
	"max_physical_memory" : "768",
	"dataset_uuid": "3766d58c-d777-11e1-89c1-4fa1b8ed5c1e",
	"resolvers": [
		"208.67.220.220",
		"208.67.222.222"  
	],
	"nics": [
		{
		  "nic_tag": "admin",  
		  "ip": "dhcp"  
		}  
	]
}

Go ahead and zlogin jenkins-slave and you should be logged into the machine. We’ll need to create a user that the Jenkins server can log in a do some work.

groupadd jenkins
useradd -g jenkins -d /var/jenkins -s /bin/bash -m -c "Jenkins" jenkins
passwd -N jenkins
passwd jenkins

Back on the master server, you’ll need to create some SSH keys.

ssh-keygen -t rsa

You’ll need to setup the public key on the slave machine. Make sure that you log into the slave box from the master to accept the host key.

On the slave machine, you’ll need to install some software:

pkgin in sun-jdk6-6.0.26 scmgit gmake gcc47

This will make sure the software you need is there. If you install ruby or any other software on the master, you will need to also install it on the slave as well.

You can reference this documentation to configure Jenkins. You’ll be launching the slave via SSH.



Published

03 August 2012

Category

devops

Tags