www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reynold Xin (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (INFRA-9988) Spark GitHub PRs didn't get closed automatically after merge
Date Tue, 14 Jul 2015 08:06:05 GMT

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

Reynold Xin edited comment on INFRA-9988 at 7/14/15 8:05 AM:
-------------------------------------------------------------

Is this related to the recent github delay?

[~ke4qqq] To be honest we have been pretty frustrated with the frequency of issues w.r.t.
github integration. I understand it is not an easy job to maintain this service. In the past
I have proposed some alternatives, including:

(1) granting a small set of committers push privilege so we can apply manual sync and can
continue the development when the sync goes down. This is especially important towards the
end of a release cycle for a project.
(2) setup a separate jenkins job to do the sync. That would require granting the jenkins job
credential to do the push. The idea is that it'd be much easier for us to make sure a Jenkins
job runs continuously, rather than infra ensuring github sync works for all projects in ASF.

Unfortunately, these proposals have not been treated with respect and open discussions. In
some cases, it was dismissed quickly with the repsonse from infra saying this wouldn't happen
again because a known problem was fixed (e.g. moved the sync to a dedicated infrastructure).
In an extreme case, it was treated with mockery by a board member:

"On Thu, Mar 12, 2015 at 12:26 AM, Greg Stein <gstein@gmail.com> wrote:
I have faith our Infra people can keep a cron job running, and using Jenkins-as-cron is the
proverbial nuclear bomb as a flyswatter."


I do think we/infra have to do something here, either by migrating entirely to GitHub, or
opening up permissions to a small group of committers and ask the small group to use the permission
judiciously (only for sync), or let us setup a separate sync job (using Jenkins or not), or
another clever solution that infra comes up with.


was (Author: rxin):
Is this related to the recent github delay?

[~ke4qqq] To be honest we are pretty frustrated with the frequency of issues w.r.t. github
integration. I understand it is not an easy job to maintain this service. In the past I have
proposed some alternatives, including:

(1) granting a small set of committers push privilege so we can apply manual sync and can
continue the development when the sync goes down. This is especially important towards the
end of a release cycle for a project.
(2) setup a separate jenkins job to do the sync. That would require granting the jenkins job
credential to do the push. The idea is that it'd be much easier for us to make sure a Jenkins
job runs continuously, rather than infra ensuring github sync works for all projects in ASF.

Unfortunately, these proposals have not been treated with respect and open discussions. In
some cases, it was dismissed quickly with the repsonse from infra saying this wouldn't happen
again because a known problem was fixed (e.g. moved the sync to a dedicated infrastructure).
In an extreme case, it was treated with mockery by a board member:

"On Thu, Mar 12, 2015 at 12:26 AM, Greg Stein <gstein@gmail.com> wrote:
I have faith our Infra people can keep a cron job running, and using Jenkins-as-cron is the
proverbial nuclear bomb as a flyswatter."


I do think we/infra have to do something here, either by migrating entirely to GitHub, or
opening up permissions to a small group of committers and ask the small group to use the permission
judiciously (only for sync), or let us setup a separate sync job (using Jenkins or not), or
another clever solution that infra comes up with.

> Spark GitHub PRs didn't get closed automatically after merge
> ------------------------------------------------------------
>
>                 Key: INFRA-9988
>                 URL: https://issues.apache.org/jira/browse/INFRA-9988
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Git
>            Reporter: Xiangrui Meng
>            Assignee: Geoffrey Corey
>
> Many recent PR remained open after merge, for example, https://github.com/apache/spark/pull/7367.
This might be related to INFRA-9782. Since this issue happens from time to time, it would
be nice to grant Spark PMCs (or committers) access to close PRs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message