|
||||||||
|
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 spent a while trying to follow the "No new revisions were found; the most-recently built branch will be built again" lead.
As far as I can tell, Jenkins seems to be hitting a code path where it believes that it isn't polling, and that it was told that it has to build something (as if someone clicked the Build Now link). Specifically, I think it’s reaching the determineRevisionToBuild() method at line 790 of https://github.com/jenkinsci/git-plugin/blob/616da8a1124b103c351e275540bce6eec9ce2959/src/main/java/hudson/plugins/git/GitSCM.java, which calls getBuildChooser().getCandidateRevisions() with a first parameter of false, indicating that it is NOT in a polling codepath. It seems that it most likely is getting there from the checkout() method at line 887, but I couldn't trace any further than that.
Is this enough of a lead for someone (more familiar with the Jenkins codebase than I am) to figure out why polling might be hitting a code path that eventually calls getBuildChooser().getCandidateRevisions() with a parameter that says it is not polling?