installing the software for the jenkins certification examFebruary 27th, 2016 by Jeanne Boyarsky
I didn’t have Jenkins on my home machine. While I do use it at CodeRanch and at work, I can’t just make changes because I feel like experimenting so installed locally. So I installed Jenkins on my home computer so I could practice for the Jenkins certification exam. The first thing I did was download the version in the study guide.
Also, see my main blog post about the Jenkins certification exam
Note: this is an old version with known security issues but it is what the PDF says questions were created against so using it anyway.
Installing Jenkins Enterprise
Since it was local and just for playing, I don’t need a servlet container and could just kick it off. Nice and easy:
- Download war from http://mirrors.jenkins-ci.org/war/1.625/
- java -jar jenkins.war
- Launch at http://localhost:8080
Note: <home>/.jenkins has all data from this test install
Then I installed the Jenkins Enterprise edition using the evaluation license. I choose “Install license only” as described on the wiki. It would have been better to choose the full enterprise option to get all the plugins so I circled back and did that.
Note the license is only valid for two weeks so plan carefully!
A few plugin names differed between the JDF and what was available:
- Disk-usage-plugin vs Disk usage plugin
- Jabber notifier plugin vs jabber plugin
- Node and Label Parameter Plugin vs Nodelabel parameter plugin
- Pipeline: Multi-Branch vs Multi-Branch pipeline
I also added the literate plugin which is referenced in objectives, but not in the plugin list in the PDF. Finally, I installed the File System SCM plugin so I didn’t have to put everything I build in local git to test things.
There were some plugins I wasn’t sure if I had based on the PDF names:
- Client Masters
- Cluster Operations
- Shared cloud
- Shared slaves
- Pipeline Checkpoints Plugin (formerly known as Pipeline Checkpoints Plugin)
Installing Cloudbees Jenkins Operations Center
I had never used Cloudbees Jenkins Operations Center (CJOC) before. I downloaded the war and set my JENKINS_HOME variable. Then I started the CJOC:
java –jar jenkins-oc.war –httpPort=8081 –prefix=/operations-center
And accessed it at http://localhost:8081/operations-center/registration
Note: I realized 3 days before the test that anyone can get an account to edit the Jenkins wiki and fix typos (fixed one at that point). I wish I had realized this earlier as I saw a few others.