Skip to Content

Installing and Configuring Jenkins Build Server

Version 58.1 by David Avendasora on 2011/07/07 13:31
Warning: For security reasons, the document is displayed in restricted mode as it is not the current version. There may be differences and errors due to this.

Jenkins is an "extensible continuous integration server".  It monitors repeated executions of jobs, such as building software projects, and can be used to build WebObjects applications and frameworks.  Hudson is an open source project, and can be used at no cost.  An introductory presentation on building WebObjects projects with Hudson (the predecessor to Jenkins) was given by Mike Schrag at WOWODC-West in 2009, and the video can be purchased from wocommunity.org.

Upgrading from Hudson

Switching from Hudson to Jenkins is straight-forward since Hudson was the foundation that Jenkins was forked from. jenkins-ci.org has a wiki entry to help with the change.

Stand-Alone Mac OS X Setup

  1. Download the Jenkins Binary Installer from the Jenkins Website.
    The direct link to get he latest installer is: http://mirrors.jenkins-ci.org/osx/latest. This will download a standard OS X Installer Package named jenkins-n.nnn.pkg.
  2. Run the installer
    JenkinsInstaller.png
  3. Restart your computer
    This is required because the current version of Jenkins does not create the its directory until it launches after you restart you computer.
  4. Point your browser to: http://localhost:8080/
  5. Start setting up jobs (Instructions from WOWODC2011 Coming Soon)

Using SSL

Setting up SSL for Jenkins is surprisingly easy. The following is originally from the SSL Setup Options page on nabble.com:

  1. Create a selfsigned test SSL certificate. 
    keytool genkey keyalg RSA alias selfsigned keystore keystore.jks -storepass ToPSecRet321 dname "cn=localhost"
  2. Launch Hudson. 

Unknown macro: noformat. Click on this message for details.

  1. Launch browser 
    Open "https://localhost:8080" in browser. You might get a browser warning, because the certificate is not signed by a known certificate authority. Communication is SSL-encrypted nevertheless.
Warning

Please Note

The port has changed from the original instructions. That was required on Mac OS X because of permissions. Also, it's worth noting that the keytool asks for a second password for the private key of the ssl certificate. We are using the same password as the keystore password and everything works. It is unclear if that makes a difference.

Servlet Container Installation on Mac OS X (10.5, 10.6)

  1. Install Tomcat from http://www.macports.org with the command

Unknown macro: noformat. Click on this message for details.

  1. Create an administrative user in /opt/local/share/java/tomcat6/conf/tomcat-users.xml.

<?xml version='1.0' encoding='utf-8'?>
<tomcat-users>
<role rolename="manager"/>
<role rolename="admin"/>
<user username="tomcat" password="tomcat" roles="admin,manager"/>
</tomcat-users>

Don't forget to change the username and password after you have finished checking out the build server and start using it in production.

  1. Start Tomcat.

Unknown macro: noformat. Click on this message for details.

  1. Download Hudson, saving hudson.war somewhere for later.
  2. Create a folder for Hudson to work in: /opt/local/var/db/hudson
  3. Change ownership of that folder: chown www:_www /opt/local/var/db/hudson
  4. Add the following to /opt/local/share/java/tomcat6/conf/setenv.local:

Unknown macro: noformat. Click on this message for details.

  1. Install Hudson in Tomcat: go to http://localhost:8080, login with the user and password that you have created in tomcat-users.xml, and upload hudson.war to the Tomcat server.
  2. Goto http://localhost:8080/hudson and you can start configuring your Hudson build server.

Unknown macro: color. Click on this message for details.

  1. Tomcat is by default installed on Mac OS X Server.
  2. Create an administrative user in&nbsp;/Library/Tomcat/conf/tomcat-users.xml.

<?xml version='1.0' encoding='utf-8'?>
<tomcat-users>
<role rolename="manager"/>
<role rolename="admin"/>
<user username="tomcat" password="tomcat" roles="admin,manager"/>
</tomcat-users> 

{color:#000000}Don't forget to change the username and password after you have finished checking out the build server and start using it in production.&nbsp;{color}

  1. The way to start it depends on the version. The current way is to go to the Web Settings in Server Admin, Settings, General, check the Tomcat checkbox. Restart the WebServer.&nbsp;
  2. Unknown macro: color. Click on this message for details.
    Unknown macro: color. Click on this message for details.
    http://hudson-ci.org/latest/hudson.war, saving&nbsp;hudson.war&nbsp;somewhere for later.
  3. Create a folder for Hudson to work in:&nbsp;/Library/hudson
  4. Change ownership of that folder:&nbsp;chown appserver:sys /Library/Hudson
  5. Add the following to&nbsp;/Library/Tomcat/bin/setenv.sh:

Unknown macro: noformat. Click on this message for details.

  1. Make sure that you are using UTF8 in the Connector, by adding

Unknown macro: noformat. Click on this message for details.

to the Connector in /Library/tomcat/conf/server.xml in such a way:

Unknown macro: noformat. Click on this message for details.

  1. Install Hudson in Tomcat: go to http://localhost:8080, login with the user and password that you have created in tomcat-users.xml, and upload hudson.war to the Tomcat server.
  1. Goto http://localhost:8080/hudson&nbsp;and you can start configuring your Hudson build server.

Building WO Apps

  • Check out sh