You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Jake Farrell (JIRA)" <ji...@apache.org> on 2014/02/22 14:21:19 UTC
[jira] [Closed] (INFRA-7367) Grant AMPLab jenkins privilege on
Spark github repo for Commit Status API
[ https://issues.apache.org/jira/browse/INFRA-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jake Farrell closed INFRA-7367.
-------------------------------
Resolution: Won't Fix
Hi Reynold, would recommended that you transition to using the Apache Jenkins instance (builds.apache.org), details on access can be found here [1]. The Apache Jenkins instance has all the correct credentials and mailing list permissions you are looking for all ready setup
http://wiki.apache.org/general/Jenkins
> 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
>
> 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)