Hi, I must have been missing something, or I wasn't explaining myself well:
I can not modify job A. All the changes must be in job B and only in job B. I used to do what you offered but now I have been told that I can't define anything in job A (not my job), so everything must be defined in job B. I'm not sure this is possible in Jenkins but I hope I'm wrong... Thank you for your help Amit On Wednesday, April 9, 2014 1:24:09 PM UTC+3, Brosh, Yossi wrote: > > BTW , > > You can use Flow (under Build Triggers) to manage your jobs with params , > like : > > > > build( "b", p1: params["p1"], p2: params["p2"]) > > > > *From:* [email protected] <javascript:> [mailto: > [email protected] <javascript:>] *On Behalf Of *Brosh, Yossi > *Sent:* Wednesday 09 April 2014 13:19 > *To:* [email protected] <javascript:> > *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:* [email protected] <javascript:> [ > mailto:[email protected] <javascript:>] *On Behalf Of *Amit Weiss > *Sent:* Wednesday 09 April 2014 12:36 > *To:* [email protected] <javascript:> > *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:* [email protected] [mailto:[email protected]] *On > Behalf Of *Amit Weiss > *Sent:* Wednesday 09 April 2014 11:57 > *To:* [email protected] > *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 [email protected]. > 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 [email protected] <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 [email protected] <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 [email protected]. For more options, visit https://groups.google.com/d/optout.
