[JIRA] (JENKINS-41377) Polling has not run yet, although received push event

1,293 views
Skip to first unread message

yuvals@perfectomobile.com (JIRA)

unread,
Jan 24, 2017, 10:56:01 AM1/24/17
to jenkinsc...@googlegroups.com
yuval shalgi created an issue
 
Jenkins / Bug JENKINS-41377
Polling has not run yet, although received push event
Issue Type: Bug Bug
Assignee: Kirill Merkushev
Components: github-plugin
Created: 2017/Jan/24 3:55 PM
Environment: Ubuntu
Jenkins ver. 2.32.1
GitHub plugin 1.25.1
GitHub API Plugin1.84

Priority: Major Major
Reporter: yuval shalgi

some projects get the pushevent from github, but polling does not start
in jenkins log i see:
Received PushEvent for https://github.com/<reponame>

this is the same as configured in the job.
however polling does not start...

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

yuvals@perfectomobile.com (JIRA)

unread,
Jan 24, 2017, 10:58:01 AM1/24/17
to jenkinsc...@googlegroups.com
yuval shalgi updated an issue
Change By: yuval shalgi
some projects get the pushevent from github, but polling does not start
in jenkins log i see:
Received PushEvent for https://github.com/<reponame>

this is the same as configured in the job.
and i did check "GitHub hook trigger for GITScm polling"
however polling does not start... for other jobs with other repository it's working fine... how can i understand what going on ?

yuvals@perfectomobile.com (JIRA)

unread,
Jan 24, 2017, 11:43:05 AM1/24/17
to jenkinsc...@googlegroups.com
yuval shalgi updated an issue
some projects get the pushevent from github, but polling does not start for that job.
in jenkins log i see:
Received PushEvent for https://github.com/<reponame>

this is the same as configured in the job.
and i did check checked "GitHub hook trigger for GITScm polling" .
the github link works.

however polling does not start... for other jobs with other repository it's working fine... how can i understand what going on ?

gentoo.integer@gmail.com (JIRA)

unread,
Feb 9, 2017, 11:31:01 AM2/9/17
to jenkinsc...@googlegroups.com

subhajit.andaman@gmail.com (JIRA)

unread,
Apr 29, 2019, 3:01:14 AM4/29/19
to jenkinsc...@googlegroups.com

I am facing same problem . Here is my observations 

  1. Git hub is delivering the payloads 

=========================================================================

 

Request URL:

http://jenkins:8080/github-webhook/

Request method:

POST

content-type:

application/json

Expect:

 

User-Agent:

GitHub-Hookshot/632ecda

X-GitHub-Delivery:

24ec185c-6a48-11e9-87d5-45299c7467cb

X-GitHub-Enterprise-Host:

github.houston.softwaregrp.net

X-GitHub-Enterprise-Version:

2.16.1

X-GitHub-Event:

push

===========================================================================

2. I am able to that job got poked in http://jenkins:8080/log/all

here is the logs 

 
Apr 28, 2019 11:29:30 PM INFO org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber$1 run
Poked xxxxx-yyyyyy-zzzzzzz-CI
Apr 28, 2019 11:30:00 PM WARNING hudson.triggers.Trigger checkTriggers
 

3. But git hub log is getting updated in below . Its displaying some old log .

 

http://jenkins:8080/job/jenkins_job/GitHubPollLog/

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

subhajit.andaman@gmail.com (JIRA)

unread,
Apr 29, 2019, 3:02:06 AM4/29/19
to jenkinsc...@googlegroups.com
Subhajit Dutta edited a comment on Bug JENKINS-41377
I am facing same problem . Here is my observations 
# Git hub is delivering the payloads 

=========================================================================

 

*Request URL:*

[ http://jenkins:8080/github-webhook/ ]

*Request method:*

POST

*content-type:*

application/json

*Expect:*

 

*User-Agent:*

GitHub-Hookshot/632ecda

*X-GitHub-Delivery:*

24ec185c-6a48-11e9-87d5-45299c7467cb

*X-GitHub-Enterprise-Host:*

github.houston.softwaregrp.net

*X-GitHub-Enterprise-Version:*

2.16.1

*X-GitHub-Event:*

push

===========================================================================

2. I
am able to can see that job jenkins  got poked in here     [http://jenkins:8080/log/all|http://sac-hvm00419.swinfra.net:8080/log/all]


here is the logs 

 
Apr 28, 2019 11:29:30 PM INFO org.jenkinsci.plugins.github.webhook.subscriber.DefaultPushGHEventSubscriber$1 run
Poked xxxxx-yyyyyy-zzzzzzz-CI
Apr 28, 2019 11:30:00 PM WARNING hudson.triggers.Trigger checkTriggers
 

3. But git hub log is getting updated in below . Its displaying some old log .

 

authentication.dh@gmail.com (JIRA)

unread,
May 8, 2019, 6:28:02 AM5/8/19
to jenkinsc...@googlegroups.com
D D commented on Bug JENKINS-41377

Same here.

  • Webhook configured in GitHub.
  • Pipeline configured (GitHub hook trigger for GITScm polling)
  • System logs of Jenkins showing each of the webhooks.
  • Custom logs mentionned in wiki showing nothing.
  • Last GitHub Push page of project showing nothing (Polling has not run yet).

ricardofas@gmail.com (JIRA)

unread,
May 21, 2019, 11:55:02 AM5/21/19
to jenkinsc...@googlegroups.com

+1

same here

only happens with pipeline job

workaround:   Create a freestyle project like "Trigger pipeline job"  that will call the pipeline job  (trigger other projects..) . 

saulcrobles@gmail.com (JIRA)

unread,
Jul 17, 2019, 10:45:02 AM7/17/19
to jenkinsc...@googlegroups.com

Did you find the fix yuval shalgi

 

Exactly same issue here

yuvals@perfectomobile.com (JIRA)

unread,
Jul 17, 2019, 1:29:03 PM7/17/19
to jenkinsc...@googlegroups.com

try to copy to a new job, see if it happens in the new one.

peng_ed@yahoo.com (JIRA)

unread,
Aug 7, 2019, 9:58:01 PM8/7/19
to jenkinsc...@googlegroups.com
Ed Peng commented on Bug JENKINS-41377

Point 2 from this comment worked for me: https://github.com/jenkinsci/bitbucket-push-and-pull-request-plugin/issues/19#issuecomment-489326391

2. Did you trigger for the first time the job manually? That's necessary if you are using a pipeline job.

 

timothy.tippens@gmail.com (JIRA)

unread,
Nov 19, 2019, 12:33:03 PM11/19/19
to jenkinsc...@googlegroups.com

Is the necessary manual trigger of the first job considered a bug or a "feature" we will have to document and live with for the foreseeable future?

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

lx89757@126.com (JIRA)

unread,
Dec 11, 2019, 9:22:05 PM12/11/19
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages