|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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/groups/opt_out.
I've tested this further and it seems there's two ways to trigger a downstream project. One is as a PostBuildStep , where you can choose to block or not, and the other is a PostBuildAction. If doing it as a PostBuildStep, it is not recognized by Jenkins as a dependency, and does not appear in the Dependency View Plugin or the Pipeline plugin. If you add a PostBuildAction of "Trigger Parameterized Build on other projects" it DOES get recognized as a downstream dependency , and appears in the afforementioned plugins. So, is this intentional, or an oversight. We have been mainly using PostBuildSteps, as it allows you to block and wait......but now .... as you've seen ....our Dependency View is somewhat anaemic.