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

["Reynold Xin (JIRA)" <ji...@apache.org>]

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

Reynold Xin commented on INFRA-7367:
------------------------------------

Thanks for the response. I am still new to the process, but I have seen a lot of other ASF projects granting TravisCI permission to use the git commit status api. Is there any difference between this?

It has been brought up many times in the past few days on the Spark developer mailing list that the Jenkins messages are introducing too much noise. It makes it harder to find information in the list. While we are certainly interested in streamlining the CI process to use Apache Jenkins, it will take a long time to do because it is a non-trivial amount of work (including resource provisioning, making sure the long running CI pipelines work well). I am wondering if we can grant the AMPLab Jenkins permission first, and then explore the transitioning to Apache Jenkins later. 

> 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
>
> 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.1.5#6160)