Trying out Jenkins

January 15th, 2016

Jenkins seems to be the top code build, integration and QA automation tool to support continuous delivery.

Jenkins allows me to kick of jobs on a schedule or ofter certain events and Jenkins will keep track of the status of the jobs and the results.

To get Jenkins installed,  I read   and then read to try my first Jenkins example.

I installed Jenkins  on one of the VMs from the “landshark” demo environment for Delphix Express. Landshark consists of two Linux Centos VMs that provide source and target examples for Delphix Express. I used the “target” VM but could have just as easily used the “source” machine.

Installing Jenkins

To install Jenkins I did:

sudo wget -O /etc/yum.repos.d/jenkins.repo

sudo rpm --import

sudo yum install jenkins


service jenkins start

This gives the message “OK” but actually Jenkins dies. The workaround was to edit /etc/sysconfig/jenkins and change




also starting jenkins by hand worked even without workaround

cd /usr/lib/jenkins 
java -jar jenkins.war

I then accessed the Jenkins console at    http://my_linux_vm:8080

Running Jenkins

Click on “create new jobs”

Screen Shot 2015-12-23 at 1.13.55 PM

Name the job

Select “Freestyle project”

Screen Shot 2015-12-23 at 1.14.17 PM

Schedule the “date” command to be run and every 5 minutes by doing:

  • Fill in “Build Triggers” by checking “Build periodically” and type in “H/5 * * * *”
  • Under build choose “Execute Shell” and type in “echo `date`”

Screen Shot 2015-12-23 at 1.15.52 PM

After hitting “Save”, then letting 5 minutes pass you’ll see a new entry in “Build History” in the bottom left. Click on the “#1″.

Screen Shot 2015-12-23 at 1.21.27 PM

Then click “Console Output”

Screen Shot 2015-12-23 at 1.21.38 PM

and you will see the output of the shell script we scheduled to be run every 5 minutes.

Screen Shot 2015-12-23 at 1.21.51 PM



  1. Trackbacks

  2. No trackbacks yet.

  2. No comments yet.

6 + = nine