Status: Resolved (View Workflow)
Upstream-Projects are not recognized by Maven-plugin, when defined in a Maven-job by "Build after other projects are build":
Setup "job A" as Freestyle Project
Setup "job B" as Freestyle Project and set "job A" as trigger (Status shows job A as Upstream Project)
Setup "job Maven-B" as Maven Project and set "job A" as trigger (Status does not show any upstream project)
When "job A" is build and finishes, "job B" is triggered, but not "job Maven-B"
You can make "job Maven-B" triggered by "job A" by setting it as a Post-Build-Action in "job A"
- is related to
JENKINS-16956 Require authentication for build triggers
JENKINS-22397 A Trigger should be able to be a DependencyDeclarer
JENKINS-25758 NPE when triggering downstream job (again)
Code changed in jenkins
User: Jesse Glick
[FIXED JENKINS-23686] Fix of
JENKINS-22397 not automatically available to overriders of buildDependencyGraph unless they were using 1.558+ and calling super.
Ought to work in next version of the plugin. (Did not have time to write a test to prove it.)
Similar behavior spotted here (Jenkins #570, #571).
This is a critical bug for 1-n jobs triggering workflows.