On Fri, 10 Mar 2017, at 15:51, JordanGS wrote: > For the following pull request > > https://github.com/jenkinsci/zap-plugin/pull/3, the > continuous-integration/jenkins/pr-merge never ran to test the build. > However, for https://github.com/jenkinsci/zap-plugin/pull/2 it did. Is > this a bug or is there a particular reason that the build was never tested?
Jenkins needs to know a PR exists in order to build it. There are many reasons why this information might not reach Jenkins, e.g. GitHub might have failed to send the webhook, or there was a network error somewhere, or Jenkins was down at the time, or (most likely) the GitHub API rate limit for ci.jenkins.io had been exceeded at the time. You can see in the logs that Jenkins indeed failed to scan the repo due to being rate limited: https://ci.jenkins.io/job/zap-plugin/indexing/events However, a build of that PR has since happened, so presumably the "poll periodically" option of the multibranch project kicked in (at a time when the rate limit hadn't been exceeded). Regards, Chris -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1489204895.4107096.907683624.199707E5%40webmail.messagingengine.com. For more options, visit https://groups.google.com/d/optout.
