infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <>
Subject [jira] [Resolved] (INFRA-16473) GitHub credentials
Date Mon, 18 Jun 2018 16:11:00 GMT


Chris Lambertus resolved INFRA-16473.
    Resolution: Won't Fix
      Assignee: Chris Lambertus

You are welcome to create a github account and put the creds in your jenkins jobs if you want
to use authenticated API rate limits. Maintaining github accounts per-project or per-build
isn't something Infra would do, and there's no way for us to get a "global" account with unlimited
rate limits.

> GitHub credentials
> ------------------
>                 Key: INFRA-16473
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Thomas Bouron
>            Assignee: Chris Lambertus
>            Priority: Major
>              Labels: #bugbash-jun2018
>         Attachments: Screen Shot 2018-05-03 at 09.06.08.png, Screen Shot 2018-05-08 at
10.37.31.png, Screen Shot 2018-05-08 at 10.44.19.png
> I’m looking to migrate our current Jenkins job to multibranch pipeline jobs (using
Jenkinsfile). Those type of jobs are nice as they handle all the branches you want + PRs automatically.
For this to work though, it requires valid GitHub credentials to scan the repos and branches
(to avoid hitting the rate API limits). However, there is no defined yet.
> I could create a personal access token for this but it feels very wrong.
> What are the best practices for this? How other projects manage that? Is it possible
for infra to create a set of credentials only for Jenkins use? Would be great!

This message was sent by Atlassian JIRA

View raw message