|
||||||||
|
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 realized that the question of lastSuccessfulBuild was spurious because what really matters is the most recent build, regardless of status. I checked all the builds and they all have the requisite linked-list entry. However, I have attached the xml for the most recent failed build. It is odd though because with a debugger attached to the server, the getSCMs method is called for several other workflow jobs before this one and they all have a non-null checkouts property for their last completed build. Its only when it gets to this, never-before-succeeded job, that the checkouts property is null. Inspecting the b variable (type WorkflowRun) for the failing case, it is indeed the last of the failed builds (build #4 in the above example), so that part looks ok. Moreover, if I run this job manually and then try the git hook, it does get past this job, cycles through several more jobs and then fails again on the next never-before-succeeded job. So this lastSuccessfulBuild question actually does seem relevant empirically.