Answers: <p>Since you're talking about making delivery/deployment decisions based on the results provided by your script(s) you need to communicate with the team(s) responsible with maintaining the official CI/CD pipeline implementation for your organisation.</p>
  
  <p>If they're using Jenkins and a particular pipeline implementation (multiple technological approaches are possible) compatible with the way you hooked up your script into Jenkins locally they may be able to directly use your approach. </p>
  
  <p>Even if that's not directly possible, there probably still are ways of including your tests in the CI/CD pipeline, only with a more or less different implementation.</p>
  
  <p>Note that there may be related technical and/or logistic questions/requirements that <em>might</em> need to be addressed depending on your organisation particularities, for example: ownership, development/maintenance process and policies, SLAs for the tests, script(s) and/or the resources for their execution.</p>
  
  <p>Even if you don't get your tests integrated at first, you can still run them for every repository commit using your private Jenkins setup and make the results available for everyone to see. In time, if those results prove useful to others they may support your initiative and help with a reconsideration of the initial decision.</p>
  
Answers: CC BY-SA 4.0
Answers: 2018-05-22T23:28:56.927Z
Answers: 2018-05-22T23:46:10.450Z
Answers: 2018-05-22T23:46:10.450Z
Answers: Dan Cornilescu
Body: <p>I have prepared the JMeter test script for my project and it tests (both functionally and performance wise) various Rest Apis. I have even coupled it with Jenkins on my local machine and also implemented performance plugin.</p>
  
  <p>Now I want to achieve CI/CD with my JMeter script wherein whenever any developer commits a code, the script runs automatically and if tests pass only then things proceed. In essence, Once the code is built, all tests should run to confirm that it behaves as the developers expect it to behave.</p>
  
  <p>How do I achieve this? Step by Step detailed instructions please as I am a QA folk and devops is a new field for me!</p>
  
Tags: <jenkins><continuous-integration><jenkins-plugins><continuous-deployment><continuous-delivery>
Title: How do I achieve Continuous Integration and Continuous Delivery (Ci-Cd) via JMeter?
UserDisplayName: Rohan Kalia
ThreadText: # How do I achieve Continuous Integration and Continuous Delivery (Ci-Cd) via JMeter?
  
  (Asked by: username_0 on 2018-05-22)
  
  I have prepared the JMeter test script for my project and it tests (both functionally and performance wise) various Rest Apis. I have even coupled it with Jenkins on my local machine and also implemented performance plugin.
  
  Now I want to achieve CI/CD with my JMeter script wherein whenever any developer commits a code, the script runs automatically and if tests pass only then things proceed. In essence, Once the code is built, all tests should run to confirm that it behaves as the developers expect it to behave.
  
  How do I achieve this? Step by Step detailed instructions please as I am a QA folk and devops is a new field for me!
  
  **Tags:** jenkins, continuous-integration, jenkins-plugins, continuous-deployment, continuous-delivery
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-05-22. Score: 1
  
  Since you're talking about making delivery/deployment decisions based on the results provided by your script(s) you need to communicate with the team(s) responsible with maintaining the official CI/CD pipeline implementation for your organisation.
  
  If they're using Jenkins and a particular pipeline implementation (multiple technological approaches are possible) compatible with the way you hooked up your script into Jenkins locally they may be able to directly use your approach.
  
  Even if that's not directly possible, there probably still are ways of including your tests in the CI/CD pipeline, only with a more or less different implementation.
  
  Note that there may be related technical and/or logistic questions/requirements that *might* need to be addressed depending on your organisation particularities, for example: ownership, development/maintenance process and policies, SLAs for the tests, script(s) and/or the resources for their execution.
  
  Even if you don't get your tests integrated at first, you can still run them for every repository commit using your private Jenkins setup and make the results available for everyone to see. In time, if those results prove useful to others they may support your initiative and help with a reconsideration of the initial decision.
  
  
  ---
  
  