Answers: <p><em>Jenkins Job</em> and <em>Jenkins Pipeline</em> are basically the same. In a pipeline you define the steps of your job as groovy code (actually it is CPS <a href="https://github.com/jenkinsci/workflow-cps-plugin" rel="noreferrer">https://github.com/jenkinsci/workflow-cps-plugin</a>, but that should in general just be a custom groovy interpreter).</p>
  
  <p>The point, that is making pipelines "better", form my perspective, is, that you can add those in so-called <code>Jenkinsfile</code>s alongside your code. So you have your build job versionized alongside your application code.</p>
  
  <p>So I would recommend: Take the time to learn how these Jenkins pipelines work and use those. But if you do not want or if you do not have the time, then doing it with plain-old Jenkins jobs is fine as well.</p>
  
Answers: CC BY-SA 4.0
Answers: 2018-07-27T19:48:38.763Z
Answers: Also note that you can create a Jenkins Pipeline and choose Git as where you want to store the source code, then use the Pipeline GUI to create the Pipeline.  The Jenkinsfile will be added to your git repo, and you can push changes to that file directly.  What I'm getting at is that you won't be forever committed to using the GUI with Pipeline.
Answers: Olivia Stork
Answers: CC BY-SA 4.0
Answers: 2018-07-26T14:04:13.710Z
Answers: 2018-07-26T14:04:13.710Z
Answers: Max N.
Body: <p><strong>BACKGROUND :</strong> We have one Selenium automation project which is shared in BitBucket repository. Project is maven project. we have 10 <code>testng.xml</code> files for all modules</p>
  
  <p><strong>OVERVIEW:</strong> Now we want to trigger the automation build once any changes committed in AUT application code.
  Also want to trigger the build for failed testcase in Post Step as well, So we will be sure with actual test failure.
  Once this execution done then it should send the email with report attachment. </p>
  
  <p><strong>PROBLEM</strong>: We are unable to decide What would be feasible Jenkins Job or Jenkins Pipeline ?</p>
  
  <p><strong>TRIALS :</strong> I have idea regarding Jenkins Job like setting up maven job and configuring post build trigger, email configuration but not clear enough as a layman. </p>
  
Tags: <jenkins><continuous-integration><jenkins-pipeline><automation><selenium>
Title: Jenkins Job vs Jenkins Pipeline
UserDisplayName: NarendraR
ThreadText: # Jenkins Job vs Jenkins Pipeline
  
  (Asked by: username_0 on 2018-07-26)
  
  **BACKGROUND :** We have one Selenium automation project which is shared in BitBucket repository. Project is maven project. we have 10 `testng.xml` files for all modules
  
  **OVERVIEW:** Now we want to trigger the automation build once any changes committed in AUT application code.
  Also want to trigger the build for failed testcase in Post Step as well, So we will be sure with actual test failure.
  Once this execution done then it should send the email with report attachment.
  
  **PROBLEM**: We are unable to decide What would be feasible Jenkins Job or Jenkins Pipeline ?
  
  **TRIALS :** I have idea regarding Jenkins Job like setting up maven job and configuring post build trigger, email configuration but not clear enough as a layman.
  
  **Tags:** jenkins, continuous-integration, jenkins-pipeline, automation, selenium
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-07-26. Score: 6 | Accepted answer
  
  *Jenkins Job* and *Jenkins Pipeline* are basically the same. In a pipeline you define the steps of your job as groovy code (actually it is CPS <https://github.com/jenkinsci/workflow-cps-plugin>, but that should in general just be a custom groovy interpreter).
  
  The point, that is making pipelines "better", form my perspective, is, that you can add those in so-called `Jenkinsfile`s alongside your code. So you have your build job versionized alongside your application code.
  
  So I would recommend: Take the time to learn how these Jenkins pipelines work and use those. But if you do not want or if you do not have the time, then doing it with plain-old Jenkins jobs is fine as well.
  
  > **Comments:**
  > **username_2**: Also note that you can create a Jenkins Pipeline and choose Git as where you want to store the source code, then use the Pipeline GUI to create the Pipeline.  The Jenkinsfile will be added to your git repo, and you can push changes to that file directly.  What I'm getting at is that you won't be forever committed to using the GUI with Pipeline.  
  
  ---
  
  