Ah yes. I have installed the promoted build plugin. I have then checked (for some reason the same option appears twice):
<https://lh3.googleusercontent.com/-DIcIBG-gbyA/U0W05spnVkI/AAAAAAAAAA4/Z9eTQ7BSiTs/s1600/promoted.png> In a job *X*. Next I selected the job *a* to trigger under Action: <https://lh6.googleusercontent.com/-f0Iz8BaYmoI/U0W2HK9cDvI/AAAAAAAAABA/DJL305P4YiY/s1600/promote2.png> But when I run the maven-release on the job *X* and it completes the job *a*is not triggered. What am I missing? On Wednesday, April 9, 2014 10:38:23 PM UTC+2, Kevin Fleming wrote: > > This is called 'promotion'. Check out the Promoted Builds plugin. > > ----- Original Message ----- > From: [email protected] <javascript:> > To: [email protected] <javascript:> > At: Apr 9 2014 16:06:41 > > I have a few maven projects A, B and C on Jenkins. I have configured the > maven-release-plugin for the projects so I can release them with a single > click on the release button. > > Now I have another project that picks up released artifacts, integrates > them and runs a QA test. Currently I trigger this QA job manually. > > Now I need to trigger this QA job automatically when either A, B or C is > being released through Jenkins. I don't want to trigger the QA job each > time a change is pushed to either A,B or C only when they have been > released. Is that possible - to trigger a job Y if a job X has been > released? > -- > 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.
