infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <>
Subject [jira] [Assigned] (INFRA-18597) Github status push for Ursalabs' buildbot
Date Thu, 01 Aug 2019 10:42:00 GMT


Gavin reassigned INFRA-18597:

    Assignee: Chris Lambertus

> Github status push for Ursalabs' buildbot
> -----------------------------------------
>                 Key: INFRA-18597
>                 URL:
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Github
>            Reporter: Krisztian Szucs
>            Assignee: Chris Lambertus
>            Priority: Major
> Dear Infra,
> Ursa-labs[1] has dedicated hardware for running builds and benchmarks for Apache Arrow.
We've set up a buildbot buildmaster instance at to schedule and these
> We already have multiple builders
> which are generally quicker than the current travis builds, so We could provide more
instantaneous feedback for the changes. There are three kind of reporters implemeneted in
ursabot [1]:
> - Review reporter: mimics the status API functionality with pull-request reviews, but
it lacks context (build url for example).
> - Comment reporter: report as a GitHub comment to the pull-request, currently buildbot
can only report on individual builds instead of buildsets, thus We can spam the PR's thread.
> - Status-push reporter: this would be the best, but requires write access for the token
We're using with (currently it is @ursabot github user)
> Could We setup the status-push reporter for apache/arrow somehow? Either via granting
write access for or using a github oauth token of
with the required `repo:status` scope?
> [1]

This message was sent by Atlassian JIRA

View raw message