title: Jenkins - How many CI/CD pipelines for a release?
body: <p>Using below Git work flow, for any release,</p>
  
  <h2><a href="https://i.stack.imgur.com/30ISR.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/30ISR.png" alt="enter image description here"></a></h2>
  
  <p>For continuous delivery, my understanding is, two Jenkins pipe lines need to be created, as shown below: </p>
  
  <p>1) Build pipeline that gets triggered on merge of every <strong>Feature</strong> branch(green) into <strong>Develop</strong> branch(Purple). Pipeline will push <code>product-x.y-snapshot.jar</code> in Nexus repo.
  Purpose of this jar is for QA testing</p>
  
  <p>2) Release pipeline that gets triggered on merge of every new <strong>Release</strong> branch to <strong>Master</strong> branch. Pipeline will push <code>product-x.y.jar</code> in Nexus repo. This jar goes in production directly.</p>
  
  <p>Both pipelines have auto-tests for every functionality.
   Same number of  autotests  run in both pipelines</p>
  
  <hr>
  
  <p>1) Does two pipelines suffice for stable release? <code>product-x.y.jar</code>
  with new features added as part of that release</p>
  
  <p>2) If yes, How binary artifactory has to be maintained for both build and release pipeline? using Nexus... please provide any reference</p>