infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Thistlethwaite (JIRA)" <>
Subject [jira] [Commented] (INFRA-15076) Allow ASF Jenkins to set status of GitHub PRs
Date Fri, 07 Sep 2018 15:08:00 GMT


Chris Thistlethwaite commented on INFRA-15076:

After a bit of digging for another issue (GitHub Pull Request Builder) I found that some/all
of the Jenkins plugins use the same API token/account (currently asfbot). This brings up two
issues, 1. asfbot doesn't have write access to all repos or the ASF org 2. We quickly burn
through the API limit if we use one account for everything. I need to find a work around for
the API limit, then we can move forward with more Jenkins integration to GitHub.

> Allow ASF Jenkins to set status of GitHub PRs
> ---------------------------------------------
>                 Key: INFRA-15076
>                 URL:
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: GitBox, Github, Jenkins
>            Reporter: John D. Ament
>            Assignee: Chris Thistlethwaite
>            Priority: Major
>              Labels: #bugbash-jun2018
> For projects using gitbox (really github as primary) it's useful for the CI tooling to
be able to update tickets or somehow mark them as in progress.  This tends to include adding
labels to PRs.
> INFRA-15075 is one such example.  I agree to not giving out access to external bots,
but the flip side is that we should have an internal bot that can do this work.  So my ask
is that we enable our Jenkins instance to be able to write to gitbox repos with features like
what's described in that ticket.

This message was sent by Atlassian JIRA

View raw message