www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Rosen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-12640) Provide codecov.io API token for Spark to Spark PMC
Date Wed, 21 Sep 2016 21:15:20 GMT

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

Josh Rosen commented on INFRA-12640:
------------------------------------

I believe that Codecov currently requires write access for reporting build statuses using
the GitHub commit status API, but AFAIK it doesn't require GitHub access for displaying coverage
reports on the Codecov website. It looks like a few Apache projects are already using Codecov
in this way: https://codecov.io/gh/apache

> Provide codecov.io API token for Spark to Spark PMC
> ---------------------------------------------------
>
>                 Key: INFRA-12640
>                 URL: https://issues.apache.org/jira/browse/INFRA-12640
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Github
>            Reporter: Josh Rosen
>
> I would like to use https://codecov.io for reporting code coverage metrics for Apache
Spark
> If Spark's tests ran on Travis CI then I would not need assistance since Travis <->
Codecov authentication works out of the box, but Spark's test currently run on Jenkins infrastructure
hosted by the Berkeley AMPLab (amplab.cs.berkeley.edu/jenkins/). As a result, we require access
to the Codecov repository upload token in order to be able to upload coverage reports. These
tokens can only be accessed by GitHub users with write access to the {{apache/spark}} repo,
which is why I need INFRA's help to obtain it.
> The token can be obtained at https://codecov.io/gh/apache/spark/settings. The token is
per-repository and thus I don't think it represents any risk to grant members of our PMC access
to the token so that we can configure coverage uploading from our CI environment.
> If you are able to grant us access to the token, could you distribute it to us by emailing
it to our PMC's private list? Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message