jenkinsci / jenkinsci/github-branch-source-plugin

[JENKINS-48408] GitHub status updating and exposing URL should be an option

Open
#1,155 3 comments 0 reactions 0 assignees View on GitHub
component:github-branch-source-plugin enhancement imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
217
Forks
398
Avg merge
30m
Merged PRs (30d)
1

Description

This is somewhat similar to -JENKINS-33151-, but all I'm looking for is to have the option to not push any metadata back to github (such as pr/branch/commit status updating), or, if that isn't possible, to hide the Jenkins URL.

 

Rationale: we are using a private Jenkins to build our open-source Github repositories (many of them per org).  Currently, all built commits and PRs get marked with our internal Jenkins URL.  This is bad.  

 

Of course we could use a public Cloudbees-hosted Jenkins, and in fact we do, but for a variety of reasons we need both (e.g.: to populate our internal artifact repos).  

 

I'd be very happy to submit a PR that adds a checkbox or some other means of controlling this behavior (any pointers would be appreciated).  Thoughts?

---
Originally reported by akom, imported from: GitHub status updating and exposing URL should be an option


  • status: In Progress
  • priority: Minor
  • component(s): github-branch-source-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 2
  • imported: 2025-12-02

Raw content of original issue

This is somewhat similar to -JENKINS-33151-, but all I'm looking for is to have the option to not push any metadata back to github (such as pr/branch/commit status updating), or, if that isn't possible, to hide the Jenkins URL.

 

Rationale: we are using a private Jenkins to build our open-source Github repositories (many of them per org).  Currently, all built commits and PRs get marked with our internal Jenkins URL.  This is bad.  

 

Of course we could use a public Cloudbees-hosted Jenkins, and in fact we do, but for a variety of reasons we need both (e.g.: to populate our internal artifact repos).  

 

I'd be very happy to submit a PR that adds a checkbox or some other means of controlling this behavior (any pointers would be appreciated).  Thoughts?

1 attachment

- [Screenshot_2017-12-06_12-06-09.png](https://issues.jenkins.io/secure/attachment/40599/Screenshot_2017-12-06_12-06-09.png)
> ![Screenshot_2017-12-06_12-06-09.png](https://issues.jenkins.io/secure/attachment/40599/Screenshot_2017-12-06_12-06-09.png)

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.