|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Where it gets complicated is if you want your pipeline to behave so that if someone commits to module K, then of course K gets rebuilt & retested, but also L–Z get rebuilt and retested. Or just some of those, in the transitive downstream dependencies of K. Presuming you do not want to manually code these dependencies, you need some kind of tool which can inspect your sources and figure them out. Traditionally this was make, but if you want to spread builds across multiple Jenkins slaves, then you would need to reimplement that kind of analysis in a Workflow script using some library built for the purpose (say, by scanning Maven POMs). It is a potentially large topic.