Manage Jenkins -→ Plugins-→ Available plugins -→ JaCoCo.

After installing from the 'Available plugins' section, verify the installation by checking the 'Installed plugins' tab in the 'Plugins' panel on the left side.

Manage Jenkins → Plugins→ Available plugins → JUnit.

After installing from the 'Available plugins' section, verify the installation by checking the 'Installed plugins' tab in the 'Plugins' panel on the left side.

Manage Jenkins → Plugins → Available plugins → Warnings.

After installing from the 'Available plugins' section, verify the installation by checking the 'Installed plugins' tab in the 'Plugins' panel on the left side.

'*' (asterisk): This will trigger a build for every change made to any branch or tag in the repository.

'origin/master': This will only trigger a build for changes made to the master branch.

'feature/*': This will trigger a build for any branch that starts with the word "feature/".

'!hotfix/*': This will trigger a build for any branch except for branches that start with the word "hotfix/".

'tags/*': This will trigger a build for any new tag pushed to the repository.

Click on the Additional Behaviors section.

Click on Add and select Sparse Checkout paths.

In the text field, enter the path(s) to the directory or file that is to be checked out.

Click Save to save the configuration.

Scroll down to the Build Environment section.

Tick the checkbox Use secret text(s) or file(s).

Click Add under the Secret text section.

In the Variable field, enter a name for the environment variable that will store the secret text. This name will be used to reference the secret text in the build scripts.

Under Credentials, select the secret text credential that is to be used. A new secret text can be created by going to Credentials > System > Global credentials (or appropriate scope) and clicking Add Credentials. Then select Secret text from the dropdown menu.

Click Save to save your configuration.

Click on Add build step.

Select Invoke top-level Maven targets from the dropdown menu and select the required maven versions and goals.

Select Execute shell from the dropdown menu.

In the text box, enter the shell command that wants to be run.

Optionally configure things like whether to capture environment variables or fail the build if the command fails.

Scroll down to the Post-build Actions section.

From the list of available actions, choose Publish JUnit test result report.

In the Test report XMLs field, specify the path to the JUnit test report files using the Ant glob syntax (similar to wildcard patterns). This pattern will match all JUnit XML files with the .xml extension located within sub-directories of target/surefire-reports (assuming that’s where the test reports are generated).

Click the Save button at the bottom of the configuration page.

Select the Record JaCoCo coverage report action.

Specify the path for JaCoCo execution data files.

These are typically generated during the build process and have a .exec extension ( e.g., target/jacoco.exec ). Use Ant path patterns for flexibility ( e.g., */target/.exec ).

Define the path to the compiled class files. This helps JaCoCo map the execution data to the source code (e.g., target/classes ).

Optionally specify the location of the source code files (e..g., src/main/java ). This allows JaCoCo to display line numbers and source code snippets in the report.

Optionally provide an Ant path pattern to exclude specific source files or directories from the coverage report.

Click the Save button to apply the configuration.

Select the Record compiler warnings and static analysis results.

Click the question mark icon (?) next to "Tool."

Select the tool from the dropdown list ( e.g., C++ compiler, static analysis tool, PMD ).

By default, the plugin searches for files named pmd.xml. If the reports use a different filename pattern, enter it here using Ant glob syntax (e.g., */target/.xml to match all XML reports in the "target" sub-directory ).

Click the Save button at the bottom of the configuration page.