jenkins-infra-bot
commented
2 years ago We'll make you a github app restricted to your application, and we'll give you access to it. It will be usable in Github Actions and/or Jenkins.
Part of https://github.com/jenkins-infra/jenkins-usage-stats/issues/2
As part of moving to using https://github.com/jenkins-infra/jenkins-usage-stats, we'll have a monthly job that will do the actual report generation, and will push the results to the gh-pages branch in https://github.com/jenkins-infra/infra-statistics. That means the job will need some creds that allow it to do that push.
I don't actually know what the state of the art for this kind of GitHub situation is these days - a deploy key in the repo? A carefully-scoped personal access token using some GH account or other? So I'll defer to you all - whatever you think best will work fine, so long as it lets us do a git push origin gh-pages to infra-statistics.git. Presumably this cred will be stored on infra.ci.jenkins.io?
Originally reported by abayer, imported from: Creds/token/key for pushing to infra-statistics' gh-pages branch