jenkins the definitive guide

Figure 2.14. Setting up your first build job in Jenkins

Once you click on OK, Jenkins will display the project configuration screen (see Figure 2.15, “Telling
Jenkins where to find the source code”).

In a nutshell, Jenkins works by checking out the source code of your project and building it in its own
workspace. So the next thing you need to do is to tell Jenkins where it can find the source code for your
project. You do this in the Source Code Management section (see Figure 2.15, “Telling Jenkins where
to find the source code”). Jenkins provides support for CVS and Subversion out of the box, and many
others such as Git, Mercurial, ClearCase, Perforce and many more via plugins.

For this project, we will be getting the source code from the GitHub repository we set up earlier.
On the Jenkins screen, choose “Git” and enter the Repository URL we defined in Section 2.2.5,
“Forking the Sample Repository” (see Figure 2.15, “Telling Jenkins where to find the source code”).
Make sure this is the URL of your fork, and not of the original repository: it should have the form
[email protected]:/game-of-life.git, where is the username for your own
GitHub account. You can leave all of the other options up until here with their default values.