Java Reference
In-Depth Information
or split of the project. Kohsuke works on the half now known as Jenkins (for a long time,
each project regarded itself as the real project and the other as the fork). Hereafter, I'll just
use the name Jenkins, because that's the one I use, and because it takes too long to say “Jen-
kins/Hudson” all the time. But almost everything here applies to Hudson as well.
Jenkins is a web application; once it's started, you can use any standard web browser as its
user interface. Installing and starting Jenkins can be as simple as unpacking a distribution
and invoking it as follows:
java -jar jenkins.war
If you do that, be sure to enable security if your machine is on the Internet! This will start up
its own tiny web server. Many people find it more secure to run Jenkins in a full-function
Java EE or Java web server; anything from Tomcat to JBoss to WebSphere or Weblogic will
do the job, and let you impose additional security constraints.
Once Jenkins is up and running and you have enabled security and are logged in on an ac-
count with sufficient privilege, you can create “jobs.” A job usually corresponds to one pro-
ject, both in terms of origin (one source code checkout) and in terms of results (one
war
file,
one executable, one library, one whatever). Setting up a project is as simple as clicking the
“New Job” button at the top-left of the dashboard, as shown in
Figure 1-12
.
