Hi Gavin, Looks like that the new credentials don’t have rights to update build status either:
https://ci-hadoop.apache.org/view/ZooKeeper/job/ZooKeeper%20PreCommit%20GitHub%20PR/view/change-requests/job/PR-1429/2/console ————— Started by user Andor Molnar 09:38:53 Connecting to https://api.github.com using 76885/****** (ASF Cloudbees Jenkins ci-hadoop) … 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 GitHub has been notified of this commit’s build result ERROR: script returned exit code 1 Finished: FAILURE ————— Andor > On 2020. Aug 14., at 9:37, Gavin McDonald <gmcdon...@apache.org> wrote: > > Hi All, > > For those of you waiting for the 'asf-ci' credentials - this is still not > resolved yet, and is waiting > for Cloudbees support. > > However - I have created some new credentials, based off of a GH App rather > than a role account. > > Look for credentials 'ASF Cloudbees Jenkins ci-builds' and give that a try > in your jobs please and see if that works for you. Let me know how it goes > for you. > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team
