Executing Scripts Using Jenkins FreeStyle Project

TABLE OF CONTENTS

1. Overview

2. Prerequisites

3. Delete an Existing Project 

4. Creating a Job and Running a Build using FreeStyle Project

1. Overview

This article provides detailed instructions for setting up Jenkins, configuring Java and Maven, creating and running a Jenkins job, and managing projects for executing Selenium scripts. It covers all necessary steps to automate builds and test executions in Jenkins using a Freestyle project.

2. Prerequisites

• Install Jenkins by following the steps described in Jenkins Installation  
• Configure Java and Maven by following the steps described in Configure Java and Maven
• Navigate to the script generated folder and open the cmd prompt by typing cmd in the Folder address bar. Run 'mvn test' command to execute the scripts, wait until 'Build Success' message is seen. This indicates that your scripts are executed successfully.

3. Delete an Existing Project 

1. In the Dashboard, to delete the existing script, select the scripts generated checkbox, as shown:
   
2. Select the Script Execution dropdown list to delete the project if there are any projects, as shown:
   
3. Click Yes to delete the project.

4. Creating a Job and Running a Build using FreeStyle Project

Perform the following:

1. In the Dashboard screen,  click Create a Job Plus icon and enter an item name.
   
2. Select Freestyle project option and click OK
   
3. In the Configure tab, select Advance Settings dropdown list.
   
4. Select Use custom workspace option.
    
5. Enter the Directory path.
   
6. Click Apply.
   
7. Click Save.
   
8. Click Configure.
   
9. Click Add build step dropdown list.
   
10. Click Invoke Top-level Maven projects option, as shown:
    
11.  Select Maven Version dropdown list.
    
12. Enter the goals and click Apply.
    
13.  Click Save.
    
14. Click Build Now.
    
15. Select the Project from the Build History, as shown:
    
16. Click  Console Output.
    
17.  Console Output contains:
    • Build Information: Details about the build number, job name, and build status. For example, success, failure test results.

    • Log Messages: Output from build steps, including commands executed, and any log messages from scripts or applications.

    • Error Messages: Warnings and error messages if something went wrong during the build or testing process.

    • Environment Variables: Information about the environment in which the build is running, such as variable values.

    • Plugin Outputs: Messages from any installed plugins that are executing during the build process.