[jira] [Closed] (INFRA-7367) Grant AMPLab jenkins privilege on Spark github repo for Commit Status API

["David Nalley (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/INFRA-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Nalley closed INFRA-7367.
-------------------------------

While the folks at GH are working on much more fine grained access; at present we can only grant a github user one of: Read, Write, or Admin privileges. 

We can theoretically, grant permissions to applications with more narrow permissions - but that's quite honestly a long term maintenance issue we're not really in a place to support. 

The ASF provides GH integration with a number of services including Jenkins at the ASF that Infrastructure manages, and you are welcome to use those, but at present we will not be granting access to external entities. 

> Grant AMPLab jenkins privilege on Spark github repo for Commit Status API
> -------------------------------------------------------------------------
>
>                 Key: INFRA-7367
>                 URL: https://issues.apache.org/jira/browse/INFRA-7367
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Git
>            Reporter: Reynold Xin
>            Assignee: Jake Farrell
>             Fix For: Mar 2014
>
>
> The Spark project accepts contributions via pull requests on github and uses Jenkins hosted by the UC Berkeley AMPLab ( account https://github.com/amplabjenkins ).
> Right now all pull request comments are forwarded to the spark dev list, resulting in a lot of noise because of the Jenkins messages ("build started", "finished", "failed", etc).
> Is it possible that we grant privilege to the amplabjenkins account so the Jenkins pull request builder can use the github commit status API without leaving lots of comments on the PRs?
> Thanks!



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