infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Leventov (JIRA)" <>
Subject [jira] [Commented] (INFRA-16674) Migrate incubating Druid Github repo to Apache
Date Wed, 18 Jul 2018 15:51:00 GMT


Roman Leventov commented on INFRA-16674:

[~cml] thanks Chris, linking the gitbox account worked.

Regarding TeamCity integration, here:
I have been told that repo:status permissions are sufficient. This page:
describes "repo:status" permissions: "Grants read/write access to public and private repository
commit statuses. This scope is only necessary to grant other users or services access to private
repository commit statuses without granting access to the code." So it doesn't give write
access to the repo code (branches, etc). Would it be possible to create an OAuth token with
such permissions?

> Migrate incubating Druid Github repo to Apache
> ----------------------------------------------
>                 Key: INFRA-16674
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Github
>            Reporter: Jonathan Wei
>            Assignee: Chris Lambertus
>            Priority: Major
> We would like to transfer the Druid github repo ( to
Apache while preserving the history of issues/PRs/stars/etc., similar to Airflow (
and Superset (
> Going forward, we also wish to keep our existing workflows and continue using Github
PRs and issues, with a similar setup as Superset (
> -------
> We're currently using the following Github integrations:
> - Travis CI
> - TeamCity
> Are these approved/supported by Apache INFRA? (I've seen Travis CI on some other projects
like Superset and Gobblin)

This message was sent by Atlassian JIRA

View raw message