BTW , You can use Flow (under Build Triggers) to manage your jobs with params , like :
build( "b", p1: params["p1"], p2: params["p2"]) From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Brosh, Yossi Sent: Wednesday 09 April 2014 13:19 To: jenkinsci-users@googlegroups.com Subject: RE: Trigger a downstream job in Jenkins without changing the upstream job Sure. Job A will call job B . On job A under "Build other projects" on clause Project to build insert B. Job B leave without any change . BR Yossi From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Amit Weiss Sent: Wednesday 09 April 2014 12:36 To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> Subject: Re: Trigger a downstream job in Jenkins without changing the upstream job Can u please elaborate this? I need to change things only on job B. Job A needs to build job B and not the other way around... On Wednesday, April 9, 2014 12:05:41 PM UTC+3, Brosh, Yossi wrote: Hi , You can use " Build other project" . From: jenkins...@googlegroups.com<javascript:> [mailto:jenkins...@googlegroups.com<javascript:>] On Behalf Of Amit Weiss Sent: Wednesday 09 April 2014 11:57 To: jenkins...@googlegroups.com<javascript:> Subject: Trigger a downstream job in Jenkins without changing the upstream job Hi! I have a problem and I'm looking for a direct solution (if possible) or a workaround. I have 2 jobs on Jenkins: job A (the upstream job) and job B (the downstream job) that needs to be triggered after job A has finished (will be triggered anyway, regardless of job A final status) I used to solve this problem with: "configuring Trigger parameterized build on other projects" set on job A and it worked perfectly fine. The thing is, I have been told that I can not do any change to job A configuation so I need to stop using the "configuring Trigger parameterized build on other projects" from job A (which I added in the past). Is there a way to configure something in job B that will trigger the job once job A is done? I noticed there is an "Build after other projects are built" but when checking this box, job B never started. In addition, in this way I cannot move parameters from job A to job B like I did before... Is there any other way (plugin or something else) that can help me define everything in job B? Thanks! Amit -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com<javascript:>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
