How to configure Third-party tools in Jenkins?

In Jenkins, configuring third-party tools primarily consists of the following steps. I will illustrate this process with a specific example, assuming we want to configure Git as the version control system.

Step 1: Install Required Plugins

1. Open Jenkins: First, log in to the Jenkins web interface.
2. Manage Jenkins: In the main interface, click the 'Manage Jenkins' option.
3. Manage Plugins: Next, click 'Manage Plugins' to search for and install the required plugins. In this example, ensure the 'Git plugin' is installed.

Step 2: Global Tool Configuration

1. Global Tool Configuration: After installing the plugins, return to 'Manage Jenkins' and click 'Global Tool Configuration'.
2. Configure Git:
   • In the 'Git' section, add a Git installation by clicking the 'Add Git' button under 'Git installations...'.
   • Enter a name as an identifier, such as 'Default Git'.
   • Specify the path to the Git executable; typically /usr/bin/git (on Linux) or the path to the specific git.exe file (on Windows).
   • If needed, enable automatic installation by selecting the 'Install automatically' option. Jenkins will then download and install Git from the internet.

Step 3: Project-Level Configuration

1. Create or Configure Project: Return to the Jenkins homepage and select an existing project or create a new one.
2. Configure Source Code Management:
   • On the project configuration page, locate the 'Source Code Management' section.
   • Select 'Git'.
   • Enter your Git repository URL in the 'Repository URL' field, for example, https://github.com/yourusername/yourproject.git.
   • If the repository is private, add credentials by clicking the 'Add' button and selecting 'Jenkins'.
   • In the pop-up dialog, choose 'Username with password' and enter your Git username and password or token.

Step 4: Save Configuration

1. Save and Apply Configuration: After completing all settings, click the 'Save' or 'Apply' button at the bottom of the page to save the configuration.

Example

In a specific project, I needed to integrate Jenkins with Git and Maven. Following these steps, I first installed the necessary plugins (Git plugin and Maven Integration plugin), then configured the paths for Git and Maven in the global tool settings. In the project configuration, I specified Source Code Management as Git and provided the repository URL. This ensures that after each code commit, Jenkins automatically triggers the build and uses Maven for building and testing the project.

By doing this, we can effectively leverage Jenkins to automate build and test processes, improving work efficiency and code quality.