infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-16473) GitHub credentials
Date Mon, 07 May 2018 02:37:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-16473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Lambertus updated INFRA-16473:
------------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

As far as I know, projects have not yet hit any API rate limits. Try it and see.


> GitHub credentials
> ------------------
>
>                 Key: INFRA-16473
>                 URL: https://issues.apache.org/jira/browse/INFRA-16473
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Thomas Bouron
>            Priority: Major
>
> 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
(v7.6.3#76005)

Mime
View raw message