You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System are you using (both controller, and any agents involved in the problem)?
RHEL 8
Reproduction steps
Setup a job that uses GitHub Branch Source
Use normal GitHub Tokens (not App credentials)
Do not configure any checks -> use the default config
Run the job
Expected Results
Nothing should happen
Actual Results
The build pipeline reads this warning multiple times: org.kohsuke.github.HttpException: {"message":"You must authenticate via a GitHub App.","documentation_url":"https://docs.github.com/rest/reference/checks#create-a-check-run"}
This already confuses our users. But whats worse: The Jenkins console log is spammed HEAVILY. Every time we see this message (which is atleast 3 times per build), it throws an exception:
Jul 07 09:00:43 jenkins[3283414]: org.kohsuke.github.HttpException: {"message":"You must authenticate via a GitHub App.","documentation_url":"https://docs.github.com/rest/reference/checks#create-a-check-run"}
Jul 07 09:00:43 jenkins[3283414]: at org.kohsuke.github.GitHubConnectorResponseErrorHandler$1.onError(GitHubConnectorResponseErrorHandler.java:62)
Jul 07 09:00:43 jenkins[3283414]: at org.kohsuke.github.GitHubClient.detectKnownErrors(GitHubClient.java:473)
Jul 07 09:00:43 jenkins[3283414]: at org.kohsuke.github.GitHubClient.sendRequest(GitHubClient.java:435)
Jul 07 09:00:43 jenkins[3283414]: at org.kohsuke.github.GitHubClient.sendRequest(GitHubClient.java:403)
Jul 07 09:00:43 jenkins[3283414]: at org.kohsuke.github.Requester.fetch(Requester.java:85)
Jul 07 09:00:43 jenkins[3283414]: at org.kohsuke.github.GHCheckRunBuilder.create(GHCheckRunBuilder.java:232)
Jul 07 09:00:43 jenkins[3283414]: at io.jenkins.plugins.checks.github.GitHubChecksPublisher.publish(GitHubChecksPublisher.java:85)
Jul 07 09:00:43 jenkins[3283414]: at io.jenkins.plugins.checks.status.BuildStatusChecksPublisher.publish(BuildStatusChecksPublisher.java:64)
Jul 07 09:00:43 jenkins[3283414]: at io.jenkins.plugins.checks.status.BuildStatusChecksPublisher$ChecksGraphListener.lambda$onNewHead$0(BuildStatusChecksPublisher.java:244)
Jul 07 09:00:43 jenkins[3283414]: at java.base/java.util.Optional.ifPresent(Optional.java:183)
Jul 07 09:00:43 jenkins[3283414]: at io.jenkins.plugins.checks.status.BuildStatusChecksPublisher$ChecksGraphListener.onNewHead(BuildStatusChecksPublisher.java:244)
Jul 07 09:00:43 jenkins[3283414]: at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.notifyListeners(CpsFlowExecution.java:1587)
Jul 07 09:00:43 jenkins[3283414]: at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.run(CpsThreadGroup.java:509)
Jul 07 09:00:43 jenkins[3283414]: at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:38)
Jul 07 09:00:43 jenkins[3283414]: at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:139)
Jul 07 09:00:43 jenkins[3283414]: at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
Jul 07 09:00:43 jenkins[3283414]: at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
Jul 07 09:00:43 jenkins[3283414]: at jenkins.util.ErrorLoggingExecutorService.lambda$wrap$0(ErrorLoggingExecutorService.java:51)
Jul 07 09:00:43 jenkins[3283414]: at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
Jul 07 09:00:43 jenkins[3283414]: at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
Jul 07 09:00:43 jenkins[3283414]: at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
Jul 07 09:00:43 jenkins[3283414]: at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
Jul 07 09:00:43 jenkins[3283414]: at java.base/java.lang.Thread.run(Thread.java:829)
It started on the 25th of May (last release) and now we get up to 5.000 Exceptions per hour and over 1 million per month. Since this logs at the WARNING level, it also overshadows other important messages.
Anything else?
It would be nice if the checks were not published automatically for all jobs but that the default is that no checks are published and only if a user configures the build behaviour to publish them, they are published.
The text was updated successfully, but these errors were encountered:
I guess caused by #341 because it now tries to publish checks with Standard Credentials. However, the GitHub Checks API is only compatible with GitHub App tokens.
Have you found any workaround for this? Did you just downgrade the plugin to previous version? I couldn't actually find any way to authenticate as an app 🤷
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
RHEL 8
Reproduction steps
Expected Results
Nothing should happen
Actual Results
The build pipeline reads this warning multiple times:
org.kohsuke.github.HttpException: {"message":"You must authenticate via a GitHub App.","documentation_url":"https://docs.github.com/rest/reference/checks#create-a-check-run"}
This already confuses our users. But whats worse: The Jenkins console log is spammed HEAVILY. Every time we see this message (which is atleast 3 times per build), it throws an exception:
It started on the 25th of May (last release) and now we get up to 5.000 Exceptions per hour and over 1 million per month. Since this logs at the WARNING level, it also overshadows other important messages.
Anything else?
It would be nice if the checks were not published automatically for all jobs but that the default is that no checks are published and only if a user configures the build behaviour to publish them, they are published.
The text was updated successfully, but these errors were encountered: