[JIRA] (JENKINS-53833) Support GitHub org-level hook without GitHub Organization folder/job

[j...@mertz.fm (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean Mertz commented on  JENKINS-53833  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support GitHub org-level hook without GitHub Organization folder/job   
 

  
 
 
 
 

 
 We're experiencing the exact same situation:   
 
org level webhook that is working as expected 
multibranch folder setup with the GitHub plugin 
no admin access to the individual repositories wanted/needed for our GH credentials configured on Jenkins 
Disabled the "manage webhooks" flag in preferences 
getting warnings about problems registering webhooks in individual repositories 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-53833) Support GitHub org-level hook without GitHub Organization folder/job

[median...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Jones created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53833  
 
 
  Support GitHub org-level hook without GitHub Organization folder/job   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 github-api-plugin  
 
 
Created: 
 2018-09-28 17:49  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Nick Jones  
 

  
 
 
 
 

 
 We have a single org-level webhook in GitHub Enterprise that notifies our Jenkins master (and our backup master) as to changes in all the repositories within it, but we do not utilize a GitHub Organization job on the Jenkins side (in order to have more control over per-repo Multibranch Pipeline settings like clone settings, build retention, etc.). Instead of a GitHub Organization job, we have individual Freestyle, Pipeline or Multibranch Pipeline jobs as each team prefers. However, every new Jenkins job that leverages this org-level hook to trigger its builds still causes the "There were some problems while registering or removing one ore more GitHub webhooks. Would you like to view the problems?" warning, despite the "Manage webhooks" checkbox being unchecked in the Jenkins configuration. I see no benefit to having repo-level Jenkins hooks on the GitHub side (given this single org-level hook) and no desire to add another account with Admin-level rights on all the repos (as hook configuration requires), so have no need for this warning telling me about it. I've built up a long list of ignored warnings (per repo/job) on the GitHub Hooks Problems page, but it would have been preferable not to get these warnings in the first place. Is there a benefit I'm missing to repo-level hooks in this case, or a way to suppress these warnings more generally that I'm not seeing?