> For the complete documentation index, see [llms.txt](https://n-saikiran.gitbook.io/jenkins/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://n-saikiran.gitbook.io/jenkins/how-to-use-jenkins/run-jobs.md).

# 3.2 Run jobs

**Step 1**− Once the build is scheduled, it will run. The following Build history section shows that a build is in progress.

![](https://2688010703-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4S6_Ru6DkKcsrzpTPX%2F-M4S6bkgymrtvs2W0c08%2F-M4S6mYttGQKA5wPlwvC%2Fbuild_history.jpg?generation=1586405263460449\&alt=media)

**Step 2**− Once the build is completed, a status of the build will show if the build was successful or not. In our case, the following build has been executed successfully. Click on the #1 in the Build history to bring up the details of the build.

![](https://2688010703-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4S6_Ru6DkKcsrzpTPX%2F-M4S6bkgymrtvs2W0c08%2F-M4S6mYvWXuTqgPBjQNM%2Fdetails.jpg?generation=1586405263274108\&alt=media)

**Step 3**− Click on the Console Output link to see the details of the build

![](https://2688010703-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4S6_Ru6DkKcsrzpTPX%2F-M4S6bkgymrtvs2W0c08%2F-M4S6mYxpeX8MywumDpW%2Fconsole_output1.jpg?generation=1586405263708402\&alt=media)

![](https://2688010703-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M4S6_Ru6DkKcsrzpTPX%2F-M4S6bkgymrtvs2W0c08%2F-M4S6mYzSMoUYgPgeDJT%2Fconsole_output2.jpg?generation=1586405263831409\&alt=media)

Apart from the steps shown above there are just so many ways to create a build job, the options available are many, which what makes Jenkins such a fantastic continuous deployment/continuous integration tool.