infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (Jira)" <j...@apache.org>
Subject [jira] [Assigned] (INFRA-19217) Connecting Buildkite CI/CD service to apache/arrow
Date Sat, 05 Oct 2019 00:56:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-19217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Lambertus reassigned INFRA-19217:
---------------------------------------

    Assignee: Greg Stein

> Connecting Buildkite CI/CD service to apache/arrow
> --------------------------------------------------
>
>                 Key: INFRA-19217
>                 URL: https://issues.apache.org/jira/browse/INFRA-19217
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Github
>            Reporter: Wes McKinney
>            Assignee: Greg Stein
>            Priority: Major
>         Attachments: buildkite_permissions.png
>
>
> Hello,
> We are exploring using https://buildkite.com/ as a CI/CD service to enable Apache Arrow
to run its own build agents and move off of Travis CI and Appveyor. This service has been
adopted by Google's Bazel project (https://github.com/bazelbuild/continuous-integration) and
a number of other open source projects
> Buildkite requires read and write access to Commit Statuses on GitHub but no direct code
access. I believe this is the same level of permissions that Travis CI and Appveyor require.
Please see attached screenshot and advise what would be the next steps to connect a Buildkite
app to the apache GitHub organization



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message