infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Bouron (JIRA)" <j...@apache.org>
Subject [jira] [Created] (INFRA-16473) GitHub credentials
Date Wed, 02 May 2018 11:25:00 GMT
Thomas Bouron created INFRA-16473:
-------------------------------------

             Summary: GitHub credentials
                 Key: INFRA-16473
                 URL: https://issues.apache.org/jira/browse/INFRA-16473
             Project: Infrastructure
          Issue Type: Bug
          Components: Jenkins
            Reporter: Thomas Bouron


I’m looking to migrate our current Jenkins job to multibranch pipeline jobs in jenkins.
Those type of jobs are nice at it handles all the branches you want + PRs automatically. For
this to work though, it requires GitHub credentials to scan the repos and branches and avoid
hitting the rate API limits. However, there is no defined yet.

I could create a personal access token for this but this 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