infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Stein (JIRA)" <>
Subject [jira] [Updated] (INFRA-13666) Jenkins -> Github "integration" (account privileges)
Date Mon, 18 Jun 2018 17:50:00 GMT


Greg Stein updated INFRA-13666:
    Labels: #bugbash-jun2018  (was: )

> Jenkins -> Github "integration" (account privileges)
> ----------------------------------------------------
>                 Key: INFRA-13666
>                 URL:
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: Github
>            Reporter: Leif Hedstrom
>            Assignee: Daniel Gruno
>            Priority: Minor
>              Labels: #bugbash-jun2018
>          Time Spent: 1h
>  Remaining Estimate: 0h
> We have a pretty intricate Jenkins build system, across a large number of VMs. Part of
this, we have 10 VMs dedicated to run Github PR jobs. The setup is fairly restricted, only
PMC members can "trigger" builds automatically, or allow other contributors builds to be built.
> This all works well, for the most part. To notify build success / failures, we have a
Github account, "atsci", which posts comments to each PR as they succeed / fail. See for example:
> However, if we could give "atsci" some privileges, such that it could add / modify Labels
and other fields in Github, the integration would be a lot nicer. We could then for example
make sure that PRs which don't pass all build tests never get committed by a committer.
> Is this possible to do at all? We don't want atsci to commit anything, or automate any
of the process we want our committers to deal with. But allowing this minimal amount of access
(and an auth token obviously) would really make things a lot nicer.
> I hope this makes any sense, if not, please let me know if I can provide any more details.
> Thanks!

This message was sent by Atlassian JIRA

View raw message