|
||||||||
|
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.
I think that hints at a fundamental difference between your use model and the way the plugin is coded in that area. I think you want to compare against some prior point that is not the preceding build, while the plugin wants to compare against the results of the preceding build.
Can you explain further how you would envision the plugin should decide the base SHA1 for the comparison?
If the job changes freely from one unrelated branch to another, how would it assemble the list of files which changed?