infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Krisztian Szucs (JIRA)" <j...@apache.org>
Subject [jira] [Created] (INFRA-18597) Github status push for Ursalabs' buildbot
Date Tue, 11 Jun 2019 20:16:00 GMT
Krisztian Szucs created INFRA-18597:
---------------------------------------

             Summary: Github status push for Ursalabs' buildbot
                 Key: INFRA-18597
                 URL: https://issues.apache.org/jira/browse/INFRA-18597
             Project: Infrastructure
          Issue Type: Improvement
          Components: Github
            Reporter: Krisztian Szucs


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 https://ci.ursalabs.org/ to schedule and these tasks.

We already have multiple builders https://ci.ursalabs.org/#/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 https://github.com/ursabot or using a github oauth token of https://github.com/asfbuildbot
with the required {repo:status} scope?

[1] https://github.com/ursa-labs/ursabot/blob/master/ursabot/reporters.py


https://ci.ursalabs.org/#/builders



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message