Setting Jenkins Job for Beginners - Part 3

Setting Jenkins Job - Understanding SCM 

In the last post, we covered the General tab details, JDK and Label/Nodes which is used. If you want to go through the post again, use this link. Setting Up Jenkins Job - Understanding General tab

In this section, we will cover the SCM .i.e. Source Code Management in Jenkins jobs.

This is the part where the actual project from any repository either GitHub or SVN is configured.

In practice, the main Jenkins pipeline job is basically intended to only call other Jenkins jobs and do some other tasks like publishing reports, sending emails etc. It should not be handing the source code management part. But, the pipeline in the end is a Jenkins job, which if configured with the SCM, can build the configured project as well.

We will talk about Git, Multiple SCMs and Subversion in details below.

Git

The above section is where the Repository URL, credentials to connect with the repository, branches to build, different git version to choose from and repository browser can be configured.

With the above additional behaviors, you can control multiple task like cleaning the project before the checkout or after checkout, checkout to some other directory, or merge the builds etc. 

Subversion

The subversion also follows the same way as Git section explained above. It also have the repository URL, credentials to connect with the repository, module directory to build, checkout strategy and repository browser can be configured.

Multiple SCMs

In this section you can provide multiple projects that can be built. Once you click on Git or Subversion, respective section will open as explained above.

With this, we conclude the Source Code Management (SCM) section. This will help to checkout the projects you want for your Jenkins job. 

In the next section, we will cover the Build Environment sections.Setting Jenkins job - Understanding Build Environment