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

["Nicholas Chammas (JIRA)" <ji...@apache.org>]

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

Nicholas Chammas commented on INFRA-7367:
-----------------------------------------

[~jfarrell] / ASF Infra, can we revisit this issue?

According to the latest [GitHub API docs|https://developer.github.com/v3/repos/statuses/], it is possible to grant access to commit statuses without granting push access to the repo:

{quote}
Note that the {{repo:status}} [OAuth scope|https://developer.github.com/v3/oauth/#scopes] grants targeted access to Statuses *without* also granting access to repository code, while the {{repo}} scope grants permission to code as well as statuses.
{quote}

If the ASF grants the AMPLab Jenkins OAuth user access to {{repo:status}}, we will be able to set commit statuses on GitHub without having access to the code and without needing to migrate to a new CI infrastructure.

Are there any obstacles to granting us this access?

cc [~rxin] [~pwendell]

> 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)