Answers: <p>A pretty standard way of doing this would be to chain your jobs or your pipelines.  This lets you keep separate jobs (which can be useful), but lets you trigger one job from the other and visualize the end-to-end flow.</p>
  
  <p>So, you still just tell one job to run, but it runs both properly.  Their config and logs are still well separated and you get all the other isolation related benefits.</p>
  
  <p>Example: <a href="https://www.jrebel.com/blog/using-jenkins-build-pipelines" rel="nofollow noreferrer">https://www.jrebel.com/blog/using-jenkins-build-pipelines</a></p>
  
  <p>You can also do this in normal Jenkins jobs not using a pipeline; there is an option to trigger other jobs near the bottom usually.</p>
  
Answers: CC BY-SA 4.0
Answers: 2020-04-14T06:36:52.253Z
Answers: No according to my scenario my backend job is having ecs environments like thor, panther, etc.. So in our backend job people will select one of the environments listed in choice parameters of the job and deploy in that environment so in this case of parametrized trigger plugin how can i pass the parameters of my backend job in parent job so that it trigger my child jobs parameters to select the environment
Answers: suri hima
Answers: CC BY-SA 4.0
Answers: 2020-04-08T14:13:22.813Z
Answers: 2020-04-08T14:13:22.813Z
Answers: John Humphreys
Answers: <p>Yes. Use multi-job project to combine FE phase and BE phase together. Or if you used pipeline, just add those pipelines under "build" step.</p>
  
Answers: CC BY-SA 4.0
Answers: 2020-04-09T15:37:46.243Z
Answers: 2020-04-09T15:37:46.243Z
Answers: minhluantran017
Body: <p>I have two environments - front-end and back-end. My front-end deployment has  one job and my back-end deployment has another job. My team wants to deploy both front-end and back-end together. Can combine them into single job?</p>
  
  <p>Ideally, they can choose whatever environment and respective branches they required to deploy for their testings in this one job.</p>
  
Comments: CC BY-SA 4.0
Comments: 2020-04-13T22:00:33.890Z
Comments: Why not combine them into a single repo since they're dependant on one another and have a single build that results in multiple artifacts? I don't recommend using job chaining at all. Look to a publisher/subscribe model using something like pub/sub light plugin or pub/sub on the Cloudbees side.
Comments: casey vega
Tags: <jenkins>
Title: how to run multiple environments in single job in Jenkins
UserDisplayName: suri hima
ThreadText: # how to run multiple environments in single job in Jenkins
  
  (Asked by: username_0 on 2020-04-08)
  
  I have two environments - front-end and back-end. My front-end deployment has one job and my back-end deployment has another job. My team wants to deploy both front-end and back-end together. Can combine them into single job?
  
  Ideally, they can choose whatever environment and respective branches they required to deploy for their testings in this one job.
  
  **Tags:** jenkins
  
  > **Comments:**
  > **username_1**: Why not combine them into a single repo since they're dependant on one another and have a single build that results in multiple artifacts? I don't recommend using job chaining at all. Look to a publisher/subscribe model using something like pub/sub light plugin or pub/sub on the Cloudbees side.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2020-04-08. Score: 1
  
  A pretty standard way of doing this would be to chain your jobs or your pipelines. This lets you keep separate jobs (which can be useful), but lets you trigger one job from the other and visualize the end-to-end flow.
  
  So, you still just tell one job to run, but it runs both properly. Their config and logs are still well separated and you get all the other isolation related benefits.
  
  Example: <https://www.jrebel.com/blog/using-jenkins-build-pipelines>
  
  You can also do this in normal Jenkins jobs not using a pipeline; there is an option to trigger other jobs near the bottom usually.
  
  > **Comments:**
  > **username_0**: No according to my scenario my backend job is having ecs environments like thor, panther, etc.. So in our backend job people will select one of the environments listed in choice parameters of the job and deploy in that environment so in this case of parametrized trigger plugin how can i pass the parameters of my backend job in parent job so that it trigger my child jobs parameters to select the environment  
  
  ---
  
  ### Answer by username_3 on 2020-04-09. Score: 0
  
  Yes. Use multi-job project to combine FE phase and BE phase together. Or if you used pipeline, just add those pipelines under "build" step.
  
  
  ---
  
  