|
||||||||
|
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/groups/opt_out.
Workaround: enable the "force polling using workspace" additional behaviour.
The underlying cause is an overly optimistic implementation of "fast" polling (by comparing only the last built commit and the current branch tip via git ls-remote). "Fast" polling doesn't download commits until after a build decision has been made, which means there's no way for the commit inspection rules to evaluate.
I've got [a pull request](https://github.com/jenkinsci/git-plugin/pull/181) open that fixes the problem by making commit inspecting rules force the slow path; the "force polling using workspace" additional behaviour does the same thing.