infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Munteanu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-17660) Is it possible to activate Github hooks for all present and future sling- gitbox repos?
Date Thu, 17 Jan 2019 11:42:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-17660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744941#comment-16744941
] 

Robert Munteanu commented on INFRA-17660:
-----------------------------------------

Looking at the Jenkins organisation scan log

 [Thu Jan 17 10:48:51 UTC 2019] Push event to branch deployment in repository infrastructure-puppet
UPDATED event from 192.30.252.36 → 127.0.0.1 ⇒ https://builds.apache.org/github-webhook/
with timestamp

I think that:

* the webhook needs to go to https://builds.apache.org/github-webhook/
* it needs to include pushes, pull requests and repositories ( IIUC this is what the plugin
does when automatically configured - https://github.com/jenkinsci/github-branch-source-plugin/blob/6652ef13aa4eeb089ebbe7e14650dfe706bfe579/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubOrgWebHook.java#L49
)

I am not sure about the payload, but it may be possible to see what per-project hooks do and
replicate that, in the organisation scan log I see a number of repositories referenced: infrastructure-puppet,
incubator-netbeans-website, camel, wicket, etc.

> Is it possible to activate Github hooks for all present and future sling- gitbox repos?
> ---------------------------------------------------------------------------------------
>
>                 Key: INFRA-17660
>                 URL: https://issues.apache.org/jira/browse/INFRA-17660
>             Project: Infrastructure
>          Issue Type: GitBox Request
>          Components: GitBox
>            Reporter: Robert Munteanu
>            Assignee: Daniel Gruno
>            Priority: Major
>
> We're exploring moving our Jenkins setup to a Github org folder to help with building
pull requests. At the moment we don't have any hooks setup so we just poll a lot.
> This will not scale for ~300 repos and is a waste of CPU and bandwidth.
> Something which would help is infra enabling hooks for the github repos. What is important
though is that it automatically happens for new 'sling-*' repos, otherwise when we create
new repositories they will not work as expected and will be very confusing for us.
> Is this something that can be set into place?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message