infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (INFRA-13649) GitPubSub to report branch deletion events
Date Mon, 20 Mar 2017 15:27:41 GMT


ASF GitHub Bot commented on INFRA-13649:

GitHub user stephenc opened a pull request:

    [INFRA-13649] Was supposed to send push events for *every* push


You can merge this pull request into a Git repository by running:

    $ git pull patch-1

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #188
commit b68188762f87288fb1a8d0ef0b7d731cb98dc60f
Author: Stephen Connolly <>
Date:   2017-03-20T15:26:57Z

    [INFRA-13649] Was supposed to send push events for *every* push


> GitPubSub to report branch deletion events
> ------------------------------------------
>                 Key: INFRA-13649
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Git, Jenkins
>            Reporter: Stephen Connolly
>            Assignee: Daniel Gruno
>         Attachments: INFRA-13649.diff
> As part of the integration of GitPubSub into the Jenkins SCM API I noticed that we are
not getting events for refs being deleted.;a=blob;f=asfgit/hooks/;h=68051527fd3e039da376a92504f083486d809a44;hb=HEAD#l37
shows that the event is explicitly being ignored.
> This makes it impossible to disable jobs that are no longer relevant from a multi-branch
pipeline project until there is a full scan (i.e. increasing the load on the build server
by mandating all projects to scan at a high frequency)
> I'll add comments to this ticket with the format of the payload I recommend for a deletion

This message was sent by Atlassian JIRA

View raw message