infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitalii Diravka (JIRA)" <>
Subject [jira] [Commented] (INFRA-17133) Setup CircleCI for the Drill project
Date Tue, 23 Oct 2018 12:05:00 GMT


Vitalii Diravka commented on INFRA-17133:

Drill community wants to add CircleCI to Apache Drill project as a default CI instead of TravisCI.

CircleCI requirements for the permissions correspond to the GitHub Aauthorizing Oauth Apps:
This is a full description of permissions, which CircleCI requires:

There is the useful note:
Note: CircleCI only asks for permissions that are absolutely necessary. However, CircleCI
is constrained by the specific permissions each VCS provider chooses to supply. For example,
getting a list of a user’s repos from GitHub requires write access because GitHub does not
provide a read-only permission.

If you feel strongly about reducing the number of permissions CircleCI uses, consider contacting
your VCS provider to communicate your concerns.

I have noticed that Travis CI for Open Source ( requires less permissions. But
TravisCI ( requires the same permissions and Travis team is working on migrating
onto the TravisCI (

Please let me know, which permission is not allowed for Apache. I will ask CircleCI support
about that.

> Setup CircleCI for the Drill project
> ------------------------------------
>                 Key: INFRA-17133
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: CI
>            Reporter: Vitalii Diravka
>            Priority: Major
> I'd like to get CircleCI setup with Apache Drill: 
> The PR with Circle's config.yml will be merged this week: 
> Please add permissions to access for all the committers in Drill. 
> Let me know if more information is needed. 

This message was sent by Atlassian JIRA

View raw message