No action in response to a PR, even with hooks all apparently set

42 views
Skip to first unread message

Benson Margulies

unread,
Oct 27, 2016, 12:40:58 PM10/27/16
to Jenkins Users

My project has 'Hooks with Persisted Data' as the mechanism, and Pull Request Opened and Commit Changed as the triggers. I can see the hooks being fired in the github hook area.

 see that Jenkins returned this very boring 200 response.

Date: Thu, 27 Oct 2016 16:33:26 GMT
Server: Jetty(9.2.z-SNAPSHOT)
X-Content-Type-Options: nosniff


I set up the recommended additional logger, and I see nothing in there at all.

From the main Jenkins log, I see:

Oct 27, 2016 12:33:27 PM INFO org.jenkinsci.plugins.github.pullrequest.GitHubPRTrigger readyToBuildCauses
GitHub rate limit after check raas/rosapi1.5: GHRateLimit{remaining=1000000, limit=1000000, resetDate=Sun Dec 13 08:34:06 EST 48792}, consumed: 0, checked PRs: 1
Oct 27, 2016 12:33:27 PM INFO org.jenkinsci.plugins.github.pullrequest.utils.LoggingTaskListenerWrapper info
Finished GitHub Pull Request trigger check for raas/rosapi1.5 at Oct 27, 2016 12:33:27 PM. Duration: 576ms


From my job's page, I can click on PR polling log, and see:

GitHub PR Polling Log

Running GitHub Pull Request trigger check for Oct 27, 2016 12:33:26 PM on raas/rosapi1.5
GitHub rate limit before check: GHRateLimit{remaining=1000000, limit=1000000, resetDate=Sun Dec 13 08:27:08 EST 48792}
Finished GitHub Pull Request trigger check for raas/rosapi1.5 at Oct 27, 2016 12:33:27 PM. Duration: 576ms

Benson Margulies

unread,
Oct 27, 2016, 12:43:29 PM10/27/16
to Jenkins Users
And on the PR status page, here's my PR, but it has no builds, and clicking on 'rebuild' gets me 'Build not found'.
 
 #293: WS-1008: basic changes required.
Head SHA: ae9d5233a8c23d60bd173fb793990bd41328c62eAuthor: bensonIssue updated at Thu Oct 27 12:33:25 EDT 2016
Source branch: ws-1008-versions-in-rootsAuthor's email: ben...@basistech.comPR updated at Thu Oct 27 12:33:25 EDT 2016
Target branch: masterPR mergeableLast commented at null
Labels: none
Related builds:

Benson Margulies

unread,
Oct 27, 2016, 1:21:00 PM10/27/16
to Jenkins Users
I found the bottom of this one, too. I should never have turned on the elaborate github-specific whitelisting plugin, but rather read the doc:


Andreas

unread,
Dec 14, 2016, 10:41:53 AM12/14/16
to Jenkins Users
Hi Benson,

I'm experiencing the same problem that the builds are not being triggered, although the PR log states that it recognized the incoming webhook.

I don't get your answer though - how did you finally solve the problem?

Thanks!
Andreas

Benson Margulies

unread,
Dec 14, 2016, 11:35:22 AM12/14/16
to jenkins...@googlegroups.com
Andreas,

I've left the job where I was setting up Jenkins, and I don't recall any details. 

Sorry,
benson


--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/AaL9xXbCfCQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2db3bd8e-ce03-44d6-bfdb-66121aee806b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages