Thanks Chris.

I created a ticket for ZooKeeper: 
https://issues.apache.org/jira/browse/INFRA-20613

...and saw you already responded.

Andor



> On 2020. Jul 30., at 5:42, Chris Lambertus <c...@apache.org> wrote:
> 
> There is no policy per-se, we have done this in the past, specifically for 
> repo:status tokens;
> 
> INFRA-19879
> INFRA-20042
> 
> Please create an infra jira ticket. Unfortunately, it’s an extremely manual 
> process on our end, and requires Infra to create and maintain an account and 
> password+token for each project, so it’s something we try to avoid unless 
> absolutely necessary. 
> 
> Note that this only applies to repo:status. We will not provide any machine 
> tokens which would allow for repo:write.
> 
> -Chris
> 
> 
>> On Jul 29, 2020, at 9:37 AM, Joan Touzet <woh...@apache.org> wrote:
>> 
>> Infra hasn't approved these in the past. If that policy changes, I'd very 
>> much like to know about it.
>> 
>> For CouchDB we use a token on my account that I added for this purpose, 
>> limited to Apache repos only. Of course, these API calls count towards my 
>> personal limit, which affects other GitHub work that I do outside of the ASF.
>> 
>> -joan
>> 
>> On 29/07/2020 10:18, Andor Molnar wrote:
>>> I’ve created a dummy Github user for ZooKeeper, it works fine in terms of 
>>> branch scanning, but it doesn’t have permissions to update the Github Build 
>>> status at the end of each build.
>>> I think I should add it to the project as contributor/member, but not sure 
>>> how to do that.
>>> Please advise.
>>> Andor
>>>> On 2020. Jul 27., at 13:24, Andor Molnar <an...@apache.org> wrote:
>>>> 
>>>> I’m interested in this one too.
>>>> Currently I’m using regular ‘Git’ source instead of GitHub to speed up 
>>>> branch discovery, but this way I cannot run builds against Pull Requests.
>>>> 
>>>> Andor
>>>> 
>>>> 
>>>> 
>>>>> On 2020. Jul 23., at 21:38, Zoran Regvart <zo...@regvart.com> wrote:
>>>>> 
>>>>> Hi builders,
>>>>> I see some questions on this but not much conclusion currently.
>>>>> 
>>>>> What credentials should we use with GitHub SCM source? Should we use
>>>>> personal access tokens, or will there be an INFRA provided
>>>>> Jenkins-wide credential we can use (like a GitHub App[1])?
>>>>> 
>>>>> We're now at the mercy of the GitHub API limits and as more projects
>>>>> are migrated I expect that to have a big impact.
>>>>> 
>>>>> zoran
>>>>> 
>>>>> [1] 
>>>>> https://docs.cloudbees.com/docs/cloudbees-ci/latest/cloud-admin-guide/github-app-auth
>>>>> -- 
>>>>> Zoran Regvart
>>>> 
> 

Reply via email to