continuous-integration/jenkins/pr-merge check never ran for pull request

1,088 views
Skip to first unread message

JordanGS

unread,
Mar 10, 2017, 9:51:51 AM3/10/17
to Jenkins Developers
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?

Thank you, cheers.

Christopher Orr

unread,
Mar 10, 2017, 11:01:39 PM3/10/17
to jenkin...@googlegroups.com
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

JordanGS

unread,
Mar 13, 2017, 1:49:31 AM3/13/17
to Jenkins Developers
Thank you
Reply all
Reply to author
Forward
0 new messages