jenkinsci / jenkinsci/github-checks-plugin

[JENKINS-71475] Checks are sending to github.com instead of our github server

Open
#503 2 comments 0 reactions 0 assignees View on GitHub
component:github-checks-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
89
Forks
50
Avg merge
13h 55m
Merged PRs (30d)
7

Description

On Jenkins 2.401.1 and Checks API plugin 2.0.0

We upgraded github-checks-plugin] from 1.0.19 to 545.v79a_a_68b_ca_682

The plugin now thinks our GitHub API URL is https://api.github.com instead of the GitHub Enterprise servers we have configured in Manage Jenkins -> Configure System.

Replacing our GitHub Org and Repo name, the error we get is:

[GitHub Checks] Failed Publishing GitHub checks: org.kohsuke.github.GHFileNotFoundException: https://api.github.com/repos/MyOrg/MyRepo {"message":"Not Found","documentation_url":"https://docs.github.com/rest/reference/repos#get-a-repository"} 

Maybe the plugin is overriding our GitHub server config somehow? We are using http currently as well, that could also be an issue? 

---
Originally reported by cdee_bam, imported from: Checks are sending to github.com instead of our github server


  • assignee: xiongkezhi
  • status: Open
  • priority: Minor
  • component(s): github-checks-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 4
  • imported: 20260107-220949

Raw content of original issue

On Jenkins 2.401.1 and Checks API plugin 2.0.0
We upgraded github-checks-plugin] from 1.0.19 to 545.v79a_a_68b_ca_682

The plugin now thinks our GitHub API URL is https://api.github.com instead of the GitHub Enterprise servers we have configured in Manage Jenkins -> Configure System.

Replacing our GitHub Org and Repo name, the error we get is:



[GitHub Checks] Failed Publishing GitHub checks: org.kohsuke.github.GHFileNotFoundException: https://api.github.com/repos/MyOrg/MyRepo {"message":"Not Found","documentation_url":"https://docs.github.com/rest/reference/repos#get-a-repository"} 


Maybe the plugin is overriding our GitHub server config somehow? We are using http currently as well, that could also be an issue? 

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.