www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jake Farrell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-7367) Grant AMPLab jenkins privilege on Spark github repo for Commit Status API
Date Sun, 23 Feb 2014 14:40:19 GMT

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

Jake Farrell commented on INFRA-7367:

Yes, there is one ASF travis account in use. If you would like travis integration please add
a .travis.yml file to your repository trunk and we can enable it for you against your GitHub

All comments on the Apache GitHub mirrors automatically go to the dev@list. Since we do not
control the AMPLab Jenkins we can not change where it is commenting to and how it is setup.
The Apache Jenkins instance can comment on Apache Jira tickets for your project and also send
build status to the any mailing list you configure for that job. 

> 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
> Thanks!

This message was sent by Atlassian JIRA

View raw message