Executing Scripts Using Jenkins

Modified on Tue, 1 Oct at 10:56 AM

TABLE OF CONTENTS

1. Viewing the Dashboard

2. Configuring the Environmental Variables  in Jenkins

3. Creating a Job

1. Viewing the Dashboard

Perform the following:

  1. Navigate to http://localhost:8080/login?from=%2F.
    Note that note the preceding URL may vary depending on your Jenkins installation when you choose to log in. For more information, see Jenkins Documentation
  2. Login with the admin credentials. 
  3. In the Dashboard, select the scripts generated, as shown:
  4. Select the Script Execution dropdown list to delete the project if there are any projects, as shown:
  5. Click Yes to delete the project.

2. Configuring the Environmental Variables in Jenkins

Perform the following:

  1. Navigate to the Dashboard > select Manage Jenkins > Tools.

  2. Select JDK Installations dropdown list.

  3. Select Maven Installations dropdown list, enter the details as shown and save the details. Path may vary depending on your installation directory.

3. Creating a Job

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.








 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article