Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41377

Polling has not run yet, although received push event

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • github-plugin
    • None
    • Ubuntu
      Jenkins ver. 2.32.1
      GitHub plugin 1.25.1
      GitHub API Plugin1.84

      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>

      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 ?

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

          Jack Brooks added a comment -

          I seem to be experiencing this issue as well. Running on Ubuntu 16.04 with version 1.27 of the plugin. I have "GitHub hook trigger for GITScm polling" checked off in my target job. I've confirmed that GitHub is successfully pushing to Jenkins from the GitHub UI. In my normal system log, I see:

           

          Aug 03, 2017 9:50:37 PM org.jenkinsci.plugins.github_branch_source.PushGHEventSubscriber onEvent

          INFO: Received PUSH for https://github.com/myOrg/myRepo from xxx ⇒ SERVER/github-webhook/

           

          The GitHub hook log says, "Polling has not run yet." I set up my logging recorders as per the wiki and saw:

          Aug 03, 2017 10:03:35 PM FINE com.cloudbees.jenkins.GitHubWebHook$1 apply
          Calling registerHooks() for jenkins-pipeline-test
          Aug 03, 2017 10:03:35 PM INFO org.jenkinsci.plugins.github.webhook.WebhookManager$1 run
          GitHub webhooks activated for job jenkins-pipeline-test with [] (events: [PUSH])

           

          I'll note that I created a GithubOrganization job, which then faithfully responded to the PUSH and executed a build. So my configuration appears to be correct!

          Jack Brooks added a comment - I seem to be experiencing this issue as well. Running on Ubuntu 16.04 with version 1.27 of the plugin. I have "GitHub hook trigger for GITScm polling" checked off in my target job. I've confirmed that GitHub is successfully pushing to Jenkins from the GitHub UI. In my normal system log, I see:   Aug 03, 2017 9:50:37 PM org.jenkinsci.plugins.github_branch_source.PushGHEventSubscriber onEvent INFO: Received PUSH for https://github.com/myOrg/myRepo  from xxx ⇒ SERVER/github-webhook/   The GitHub hook log says, "Polling has not run yet." I set up my logging recorders as per the wiki and saw: Aug 03, 2017 10:03:35 PM FINE com.cloudbees.jenkins.GitHubWebHook$1 apply Calling registerHooks() for jenkins-pipeline-test Aug 03, 2017 10:03:35 PM INFO org.jenkinsci.plugins.github.webhook.WebhookManager$1 run GitHub webhooks activated for job jenkins-pipeline-test with [] (events: [PUSH] )   I'll note that I created a GithubOrganization job, which then faithfully responded to the PUSH and executed a build. So my configuration appears to be correct!

          Tomas Zaleniakas added a comment - - edited

          make sure you are using case sensitive characters in scm config on jenkins. because checkout works anyway, but push notifications not. so if you have myOrg/repo but in checkout you using myorg/repo thats qorking fine for cloning repo but not for push notifications. 

          Tomas Zaleniakas added a comment - - edited make sure you are using case sensitive characters in scm config on jenkins. because checkout works anyway, but push notifications not. so if you have myOrg/repo but in checkout you using myorg/repo thats qorking fine for cloning repo but not for push notifications. 

          Subhajit Dutta added a comment - - edited

          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 can see that jenkins  got poked here  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/

          Subhajit Dutta added a comment - - edited 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 can see that jenkins  got poked here   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/

          D D added a comment -

          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).

          D D added a comment - 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).

          +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..) . 

          Ricardo Santos added a comment - +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..) . 

          Saul Cruz added a comment -

          Did you find the fix yuvals

           

          Exactly same issue here

          Saul Cruz added a comment - Did you find the fix yuvals ?    Exactly same issue here

          yuval shalgi added a comment -

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

          yuval shalgi added a comment - try to copy to a new job, see if it happens in the new one.

          Ed Peng added a comment -

          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.

           

          Ed Peng added a comment - 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.  

          Tim Tippens added a comment -

          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?

          Tim Tippens added a comment - 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?

          alex li added a comment -

          same issue with gitlab JENKINS-60452

          alex li added a comment - same issue with gitlab  JENKINS-60452

            lanwen Kirill Merkushev
            yuvals yuval shalgi
            Votes:
            3 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated: