|
||||||||||||||
|
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.
Resolved/Incomplete includes the state of waiting for more information. There is an open proposal to add a dedicated status for this purpose to this JIRA instance, in which case Incomplete could be reserved for abandoned issues, but that does not seem to have been implemented yet. There needs to be some mechanism for differentiating acknowledged open bugs, from conversations that may or may not be a real bug in some component or another (i.e., support requests).
I would start by adding a logger recording hudson.triggers.SCMTrigger and hudson.triggers.Trigger at fine levels, checking $JENKINS_HOME/scm-polling.log, and generally checking log files for errors. If that turns up nothing special, use a debugger.