|
||||||||
|
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/d/optout.
Not when using Workflow. One job with one Groovy script which can work however you like, with no additional plugins.
In the case of your diamond dependency scenario, I think all that is really missing today is the aforementioned operator to skip a stage when there are no SCM changes in that area. If you do have dozens of dependencies, it would be convenient to have a library to implement this model based on a simple configuration DSL.
I do not think anything like this will or should become part of “basic Jenkins infrastructure”. The dependency & triggering logic built into Jenkins core is already far too complex. That is why we created Workflow—the existing system did not scale up to more sophisticated scenarios.