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

First pull request pipeline in a organization folder project not being created by webhook

XMLWordPrintable

      Many Github pull requests created during the day are delivered to our Jenkins instance through an organizational webhook, buy they sometimes do not create a corresponding pipeline in the organization folder.

      This is an example of pull request:
      https://github.com/elifesciences/annotations/pull/20

      This is what I found in the logs immediately after:

      elife@prod--alfred:/var/lib/jenkins/logs$ grep -r annotations jenkins.branch.OrganizationFolder.log
[Fri Nov 24 11:40:34 GMT 2017] Received Push event to branch fail_fast_on_generic_bad_response_on_post_users in repository elifesciences/annotations CREATED event from 192.30.252.34 ⇒ http://alfred.elifesciences.org:8080/github-webhook/ with timestamp Fri Nov 24 11:40:29 GMT 2017
[Fri Nov 24 11:40:34 GMT 2017] Finished processing Push event to branch fail_fast_on_generic_bad_response_on_post_users in repository elifesciences/annotations CREATED event from 192.30.252.34 ⇒ http://alfred.elifesciences.org:8080/github-webhook/ with timestamp Fri Nov 24 11:40:29 GMT 2017. Matched 1.
[Fri Nov 24 11:40:54 GMT 2017] Received Pull request #20 opened in repository elifesciences/annotations CREATED event from 192.30.252.42 ⇒ http://alfred.elifesciences.org:8080/github-webhook/ with timestamp Fri Nov 24 11:40:49 GMT 2017
[Fri Nov 24 11:40:54 GMT 2017] Finished processing Pull request #20 opened in repository elifesciences/annotations CREATED event from 192.30.252.42 ⇒ http://alfred.elifesciences.org:8080/github-webhook/ with timestamp Fri Nov 24 11:40:49 GMT 2017. Matched 1.

      (the organization folder has matched the hook to the annotations project)

      elife@prod--alfred:/var/lib/jenkins/logs$ grep -r annotations jenkins.branch.MultiBranchProject.log
[Fri Nov 24 11:40:34 GMT 2017] Received Push event to branch fail_fast_on_generic_bad_response_on_post_users in repository elifesciences/annotations CREATED event from 192.30.252.34 ⇒ http://alfred.elifesciences.org:8080/github-webhook/ with timestamp Fri Nov 24 11:40:29 GMT 2017
[Fri Nov 24 11:40:34 GMT 2017] Finished processing Push event to branch fail_fast_on_generic_bad_response_on_post_users in repository elifesciences/annotations CREATED event from 192.30.252.34 ⇒ http://alfred.elifesciences.org:8080/github-webhook/ with timestamp Fri Nov 24 11:40:29 GMT 2017. Matched 0.
[Fri Nov 24 11:40:54 GMT 2017] Received Pull request #20 opened in repository elifesciences/annotations CREATED event from 192.30.252.42 ⇒ http://alfred.elifesciences.org:8080/github-webhook/ with timestamp Fri Nov 24 11:40:49 GMT 2017
[Fri Nov 24 11:40:54 GMT 2017] Finished processing Pull request #20 opened in repository elifesciences/annotations CREATED event from 192.30.252.42 ⇒ http://alfred.elifesciences.org:8080/github-webhook/ with timestamp Fri Nov 24 11:40:49 GMT 2017. Matched 0.

      (the hook has been ignored, I guess from the Matched 0?

      

      


      The project page itself looks like this:
      
https://screenshots.firefox.com/FDd9RpeqbrHU967L/alfred.elifesciences.org
      
It shows other pull requests that have now been closed and correctly "deleted" (they stay around for 2 days as configured before being garbage-collected). I have seen it in other states before when this problem happens, for example with 1 other existing pipeline.
      


      The workaround is to wait for the scanning to take place, but we have lots of repositories so we can't do that very often (a couple of hours) not to get rate limited by the Github API.
      
            
      

      

        1. annotations-project-config.xml
          4 kB
        2. organization-config.xml
          5 kB
          


          

            








            
                        

            
    
            
        
    
            
    
            
        

            
            



    
    stephenconnolly
            Stephen Connolly
            
        
    
            
            

                                            

            
    
            
        
    
            
    
            
        

            
            



    
    giorgiosironi
            Giorgio Sironi
            
        
    
    
            

                            
            
    
            
                        
            
        
            Votes:
            
        
            
                                0
            
                                                Vote for this issue
                    
            
    
            
                            
            
        
            Watchers:
            
        
            
                                
                                
                            3
            
                                        Start watching this issue
                    
            
    
            
        
            

              









              
            
              
    
              
                    Created:
            
              
    
              
        
                                                                                                                                 
    
              

              
            
              
    
              
                    Updated:
            
              
    
              
        
                                                                                                                                 
    
              

              
            
              
    
              
                    Resolved: