[JIRA] (JENKINS-61290) Hard to see if branch was skipped because of discovery strategy

[jimkli...@gmail.com (JIRA)]

Title: Message Title

Jim Klimov edited a comment on JENKINS-61290   Re: Hard to see if branch was skipped because of discovery strategy As a stop-gap solution that I hopefully know how to make, I would add jenkins console logging right into the `isExcluded()` methods, where they `return true`, so at least part of investigation like the one I did, would become easier. This is sub-par because the message would not appear where it is helpful to people with access to the indexing job log, but at least is something... https://github.com/jenkinsci/github-branch-source-plugin/pull/284 Add Comment   This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204867.1583144626000.2600.1583151420047%40Atlassian.JIRA.