www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zoran Regvart <zo...@regvart.com>
Subject Non committer collaborators on GitHub
Date Fri, 14 Dec 2018 11:57:03 GMT
Hi Builders,
I see some projects like Apache Sling use their own GitHub accounts
via personal access tokens on GitHub. I'm guessing this is a
workaround for not having a non-committer collaborator account that
can be used to update commit status from Jenkins pipelines.

I too have created an account, I needed one just to bypass the API
limits for anonymous access[1]. But since that account is not a
collaborator on GitHub it cannot update the commit status. I.e. the
end result is:

Could not update commit status, please check if your scan credentials
belong to a member of the organization or a collaborator of the
repository and repo:status scope is selected

So one way of fixing this is to use my own GitHub account, which I'm,
understandably hesitant to do.

Another is to have this non-committer account added as a collaborator,
would this violate any ASF rules?

And, probably the best one, is to have a ASF wide GitHub account that
builds can use.

I see that `asfgit` account is used with GitHub pull request builder,
would it be possible to create a username/password credential with
personal access token and `repos:status` OAuth scope for `asfgit`
accessible to other build types (like Pipeline)?

Thanks :)

zoran

[1] https://issues.apache.org/jira/browse/INFRA-16473?focusedCommentId=16515957&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16515957
-- 
Zoran Regvart

Mime
View raw message