Figure 2.11. Configuring a JDK installation
Now go to the bottom of the screen and click on the Save button.
2.4.3. Notification
Another important aspect you would typically set up is notification. When a Jenkins build breaks, and
when it works again, it can send out email messages to the team to spread the word. Using plugins, you
can also get it to send instant messages or SMS messages, post entries on Twitter, or get people notified
in a few other ways. It all depends on what works best for your organizational culture. Email notification
is easy enough to set up if you know your local SMTP server address—just provide this value in the
Email Notification section towards the bottom of the main configuration page. However, to keep things
simple, we’re not going to worry about notifications just yet.
2.4.4. Setting Up Git
The last thing we need to configure for this demo is to get Jenkins working with Git. Jenkins comes with
support for Subversion and CVS out of the box, but you will need to install the Jenkins Git plugin to be
able to complete the rest of this tutorial. Don’t worry, the process is pretty simple. First of all, click on the
Manage Jenkins link to the left of the screen to go back to the main configuration screen (see Figure 2.8,
“The Manage Jenkins screen”). Then click on Manage Plugins. This will open the plugin configuration
screen, which is where you manage the extra features you want to install on your Jenkins server. You
should see four tabs: Updates, Available, Installed, and Advanced (see Figure 2.12, “Managing plugins
in Jenkins”).