After the installation of Artifactory, the next step is a continuous integration (CI) system. Jenkins is a fork of the Hudson CI server, which was developed by a SUN employee until SUN was lost to Oracle.
Basic installation
There are some basic requirements for the installation. If you’re running a default OpenSolaris installation, everything should be fine. Merely in a zone you’ll most likely need some additional software which can be install via pkg.
root@test:~# pkg install wget jdk
The next steps are to create a user for jenkins(we don’t want to run it as root), download the software and create the required folders.
First the new user jenkins:
root@test:~# mkdir -p /export/home root@test:~# useradd -d /export/home/jenkins -s /usr/bin/false -m jenkins
Then we need to download current jenkins version from http://mirrors.jenkins-ci.org/war/latest/jenkins.war. We will install jenkins into /opt/jenkins which has to be created first.
root@test:~# cd /opt root@test:/opt# mkdir jenkins root@test:/opt# cd jenkins/ root@test:/opt/jenkins# wget http://mirrors.jenkins-ci.org/war/latest/jenkins.war --2011-07-30 12:32:09-- http://mirrors.jenkins-ci.org/war/latest/jenkins.war HTTP request sent, awaiting response... 200 OK Length: 38358981 (37M) [application/java-archive] Saving to: `jenkins.war' 100%[========================================================>] 38,358,981 702K/s in 55s 2011-07-30 12:33:05 (679 KB/s) - `jenkins.war' saved [38358981/38358981] root@test:/opt/jenkins# chown -R jenkins:other /opt/jenkins
Jenkins as Solaris Service
The final step is to integrate jenkins into Solaris’ Service Management Facility (smf). This requires a XML config file which describes the jenkins-service.
The required file can be found here:
jenkins-smf.xml
root@test:/opt/jenkins# cd /tmp/ root@test:/tmp# wget http://www.dev-eth0.de/wp-content/uploads/2011/07/jenkins-smf.xml root@test:/tmp# svccfg import -V jenkins-smf.xml
Now we have installed jenkins as a Solaris Service and can start and stop it with the svcadm command and check it’s status with svcs.
Commands:
svcadm enable jenkins svcadm disable jenkins
The following commands will start jenkins and check if everything is ok and running.
root@test:/tmp# svcadm enable jenkins root@test:/tmp# svcs -x jenkins svc:/application/jenkins:jenkins (Jenkins Continuous Build Server) State: online since Sat Jul 30 13:34:23 2011 See: http://jenkins-ci.org/ See: /var/svc/log/application-jenkins:jenkins.log Impact: None.
That’s it, the service is up and running, now we can access the WebGui on Port 8080:
http://yourServer:8080
It should look like this
[...] you’re running a Jenkins Continous Integration System as descriped in this guide, you most likely need Ant and/or Maven to build your [...]
I used to generate the IPS package for Jenkins, and that made the installation a breeze. But I stopped doing that when I lost a ready access to a Solaris box. Maybe it’s time to resurrect that? Any chance you’d be interested in helping out?