www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicholas Chammas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-7367) Grant AMPLab jenkins privilege on Spark github repo for Commit Status API
Date Sun, 15 Feb 2015 20:05:12 GMT

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

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

[~jfarrell] [~ke4qqq] I'd like to continue the conversation about "safe" GitHub permissions
like Commit Status.

Where is the appropriate place to do that?

Side note: Why are comments in the INFRA project not formatted like in others? e.g. Like if
you want some text to link somewhere. [Google|http://www.google.com]

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

Mime
View raw message