Re:Trigger a job Y after an artifact from job X has been released?

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

This is called 'promotion'. Check out the Promoted Builds plugin.

----- Original Message -----
From: jenkins...@googlegroups.com
To: jenkins...@googlegroups.com
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 jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[dev123]

Ah yes. I have installed the promoted build plugin. I have then checked (for some reason the same option appears twice):

In a job X. Next I selected the job a to trigger under Action:

But when I run the maven-release on the job X and it completes the job a is not triggered. What am I missing?

[dev123]

I now use the conditional trigger plugin where I set the boolean token to evaluate $IS_M2RELEASEBUILD. Works fine.