Figure 4.9. Configuring Ant in Jenkins
4.6.3. Shell-Scripting Language
If you are running your build server on Unix or Linux, Jenkins lets you insert shell scripts into your
build jobs. This is handy for performing low-level, OS-related tasks that you don’t want to do in Ant
or Maven. In the Shell section, you define the default shell that will be used when executing these
shell scripts. By default, this is /bin/sh, but there are times you may want to modify this to another
command interpreter such as bash or Perl.
In Windows, the Shell section does not apply—you use Windows batch scripting instead. So, on a
Windows build server, you should leave this field blank.
4.7. Configuring Your Version Control Tools
Jenkins comes preinstalled with plugins for CVS and Subversion. Other version control systems are
supported by plugins that you can download from the Manage Plugins screen.
4.7.1. Configuring Subversion
Subversion needs no special configuration, since Jenkins uses native Java libraries to interact with
Subversion repositories. If you need to authenticate to connect to a repository, Jenkins will prompt you
when you enter the Subversion URL in the build job configuration.
4.7.2. Configuring CVS
CVS needs little or no configuration. By default, Jenkins will look for tools like CVS on the system
path, though you can provide the path explicitly if it isn’t on the system path. CVS keeps login and
password details in a file called .cvspass, which is usually in your home directory. If this is not the
case, you can provide a path where Jenkins can find this file.