jenkinsci
[JENKINS-54577] Remove github server in "Configure System" page does not have any effect
Removing the github server or github enterprise server and saving has no effect : both are still present when reloading the admin page.
Steps to reproduce :
- add a github server and a github enterprise server (just wanted to use a "github enterprise server" but it seems that credentials only appear in the "Github Server" section so I filled both section... this part is not clear at all in the UI)
- save config
- go back to "configure system" page
- remove github server (or github enterprise server) and save
- go back to "configure system" page : the config is still there
Originally reported by yogeek, imported from: Remove github server in "Configure System" page does not have any effect
- assignee:
lanwen
- status: Open
- priority: Major
- component(s): github-plugin
- resolution: Unresolved
- votes: 2
- watchers: 4
- imported: 2025-12-08
Raw content of original issue
Removing the github server or github enterprise server and saving has no effect : both are still present when reloading the admin page.
Steps to reproduce :
- add a github server and a github enterprise server (just wanted to use a "github enterprise server" but it seems that credentials only appear in the "Github Server" section so I filled both section... this part is not clear at all in the UI)
- save config
- go back to "configure system" page
- remove github server (or github enterprise server) and save
- go back to "configure system" page : the config is still there
environment
Jenkins ver. 2.121.3<br/>
github-plugin 1.29.3<br/>
Other plugins installed :<br/>
ace-editor:1.1<br/>
ansicolor:0.5.2<br/>
ant:1.9<br/>
antisamy-markup-formatter:1.5<br/>
apache-httpcomponents-client-4-api:4.5.5-3.0<br/>
artifactory:2.16.2<br/>
authentication-tokens:1.3<br/>
aws-credentials:1.23<br/>
aws-java-sdk:1.11.403<br/>
bitbucket:1.1.8<br/>
blueocean:1.9.0<br/>
blueocean-autofavorite:1.2.2<br/>
blueocean-bitbucket-pipeline:1.9.0<br/>
blueocean-commons:1.9.0<br/>
blueocean-config:1.9.0<br/>
blueocean-core-js:1.9.0<br/>
blueocean-dashboard:1.9.0<br/>
blueocean-display-url:2.2.0<br/>
blueocean-events:1.9.0<br/>
blueocean-github-pipeline:1.9.0<br/>
blueocean-git-pipeline:1.9.0<br/>
blueocean-i18n:1.9.0<br/>
blueocean-jira:1.9.0<br/>
blueocean-jwt:1.9.0<br/>
blueocean-personalization:1.9.0<br/>
blueocean-pipeline-api-impl:1.9.0<br/>
blueocean-pipeline-editor:1.9.0<br/>
blueocean-pipeline-scm-api:1.9.0<br/>
blueocean-rest:1.9.0<br/>
blueocean-rest-impl:1.9.0<br/>
blueocean-web:1.9.0<br/>
bouncycastle-api:2.17<br/>
branch-api:2.0.20<br/>
build-monitor-plugin:1.12+build.201809061734<br/>
build-name-setter:1.6.9<br/>
build-timeout:1.19<br/>
cloudbees-bitbucket-branch-source:2.2.14<br/>
cloudbees-folder:6.5.1<br/>
command-launcher:1.2<br/>
config-file-provider:3.4.1<br/>
configuration-as-code:1.3<br/>
configuration-as-code-support:1.3<br/>
credentials:2.1.18<br/>
credentials-binding:1.17<br/>
cucumber-reports:4.1.0<br/>
discard-old-build:1.05<br/>
display-url-api:2.2.0<br/>
docker-commons:1.13<br/>
docker-java-api:3.0.14<br/>
docker-plugin:1.1.5<br/>
docker-workflow:1.17<br/>
durable-task:1.27<br/>
ec2:1.41<br/>
favorite:2.3.2<br/>
git:4.0.0-beta3<br/>
git-client:3.0.0-beta5<br/>
github:1.29.3<br/>
github-api:1.92<br/>
github-branch-source:2.4.1<br/>
git-server:1.7<br/>
gradle:1.29<br/>
handlebars:1.1.1<br/>
handy-uri-templates-2-api:2.1.6-1.0<br/>
hashicorp-vault-plugin:2.2.0<br/>
htmlpublisher:1.17<br/>
ivy:1.28<br/>
jackson2-api:2.8.11.3<br/>
javadoc:1.4<br/>
jdk-tool:1.1<br/>
jenkins-design-language:1.9.0<br/>
jira:3.0.4<br/>
job-dsl:1.70<br/>
jquery-detached:1.2.1<br/>
jsch:0.1.54.2<br/>
junit:1.26.1<br/>
ldap:1.20<br/>
mailer:1.22<br/>
matrix-auth:2.3<br/>
matrix-project:1.13<br/>
maven-plugin:3.1.2<br/>
mercurial:2.4<br/>
momentjs:1.1.1<br/>
node-iterator-api:1.5.0<br/>
pipeline-aws:1.32<br/>
pipeline-build-step:2.7<br/>
pipeline-graph-analysis:1.7<br/>
pipeline-input-step:2.8<br/>
pipeline-maven:3.5.15<br/>
pipeline-milestone-step:1.3.1<br/>
pipeline-model-api:1.3.2<br/>
pipeline-model-declarative-agent:1.1.1<br/>
pipeline-model-definition:1.3.2<br/>
pipeline-model-extensions:1.3.2<br/>
pipeline-rest-api:2.10<br/>
pipeline-stage-step:2.3<br/>
pipeline-stage-tags-metadata:1.3.2<br/>
pipeline-stage-view:2.10<br/>
pipeline-utility-steps:2.1.0<br/>
plain-credentials:1.4<br/>
publish-over:0.22<br/>
pubsub-light:1.12<br/>
rebuild:1.29<br/>
resource-disposer:0.12<br/>
role-strategy:2.9.0<br/>
saml:1.1.1<br/>
scm-api:2.3.0<br/>
scoverage:1.3.3<br/>
script-security:1.48<br/>
sonar:2.8.1<br/>
sse-gateway:1.16<br/>
ssh-agent:1.17<br/>
ssh-credentials:1.14<br/>
ssh-slaves:1.28.1<br/>
structs:1.17<br/>
timestamper:1.8.10<br/>
token-macro:2.5<br/>
variant:1.1<br/>
windows-slaves:1.3.1<br/>
workflow-aggregator:2.5<br/>
workflow-api:2.31<br/>
workflow-basic-steps:2.12<br/>
workflow-cps:2.60<br/>
workflow-cps-global-lib:2.12<br/>
workflow-durable-task-step:2.26<br/>
workflow-job:2.27<br/>
workflow-multibranch:2.20<br/>
workflow-scm-step:2.7<br/>
workflow-step-api:2.16<br/>
workflow-support:2.22<br/>
ws-cleanup:0.36<br/>
1 attachment
olira:
- Original comment link
Raw content of original comment:
I can confirm this behaviour with a fresh installed Jenkins 2.164.3 and github plugin 1.29.4.
Make sure to install GitHub plugin and GitHub Organization plugin. After startup, go to configuration and follow the steps provided above.
Result: Same behaviour.
On a side Note, I also found that the DropDown in the GitHub Organization Folder for GitHub server always shows "GitHub" and the enterprise server created, However "GitHub" is not configured at all. On top of that, none of the Servers configured in the GitHub Server section of the config are listed.
When looking at the github-plugin-configuration.xml I can see my custom created Server which is shown in the GitHub Servers section, but neither the enterprise server nor a Server named "GitHub"
I can confirm this behaviour with a fresh installed Jenkins 2.164.3 and github plugin 1.29.4.
Make sure to install GitHub plugin and GitHub Organization plugin. After startup, go to configuration and follow the steps provided above.
Result: Same behaviour.
On a side Note, I also found that the DropDown in the GitHub Organization Folder for GitHub server always shows "GitHub" and the enterprise server created, However "GitHub" is not configured at all. On top of that, none of the Servers configured in the GitHub Server section of the config are listed.
When looking at the github-plugin-configuration.xml I can see my custom created Server which is shown in the GitHub Servers section, but neither the enterprise server nor a Server named "GitHub"
dankirkd:
- Original comment link
Exact same problem as reported by yogeek and olira using github-plugin 1.34.4 on Jenkins 2.346.2. Given how old this issue is I am surprised that it hasn't been addressed.
markewaite:
- Original comment link
Raw content of original comment:
I confirm that I see the same behavior on my installation, though I'm not very worried by it. If the GitHub plugin is installed, it seems reasonable that a GitHub server would be configured. If a GitHub server is not defined, it seems reasonable that it would insert a GitHub server entry in the form, ready for the administrator to complete the form.
Steps that I took while experimenting:
- Install the GitHub plugin and other plugins into Jenkins 2.361.3 as listed in plugins.txt
- Open "Manage Jenkins" and confirm that no GitHub server is listed
- Add a secret text credential that is the text of a GitHub personal access token
- Add a GitHub server in "Manage Jenkins" that uses the secret text credential
- Save the configuration and confirm that the server is saved
- Add another GitHub server in "Manage Jenkins" that uses the secret text credential
- Save the configuration and confirm that two servers are visible
- Delete one of the servers and confirm that only one server is visible and that server is in the XML file
- Delete the remaining server and confirm that the server remains in the XML file even though it is removed from the page
- Add a new server and confirm that the new server replaces the existing server in the XML file
Expected Behavior
Deleting the last GitHub server from Manage Jenkins should remove that server.
Actual Behavior
The user action to delete the last GitHub server does not change the configuration file. The last server will reappear the next time configuration is read, either by restart or by configuration reload.
Workaround
Edit the github-plugin-configuration.xml file and remove the last entry with a text editor.
- Install the GitHub plugin and other plugins into Jenkins 2.361.3 as listed in plugins.txt
I confirm that I see the same behavior on my installation, though I'm not very worried by it. If the GitHub plugin is installed, it seems reasonable that a GitHub server would be configured. If a GitHub server is not defined, it seems reasonable that it would insert a GitHub server entry in the form, ready for the administrator to complete the form.
Steps that I took while experimenting:
- Install the GitHub plugin and other plugins into Jenkins 2.361.3 as listed in JENKINS-54577">plugins.txt
- Open "Manage Jenkins" and confirm that no GitHub server is listed
- Add a secret text credential that is the text of a GitHub personal access token
- Add a GitHub server in "Manage Jenkins" that uses the secret text credential
- Save the configuration and confirm that the server is saved
- Add another GitHub server in "Manage Jenkins" that uses the secret text credential
- Save the configuration and confirm that two servers are visible
- Delete one of the servers and confirm that only one server is visible and that server is in the XML file
- Delete the remaining server and confirm that the server remains in the XML file even though it is removed from the page
- Add a new server and confirm that the new server replaces the existing server in the XML file
Expected Behavior
Deleting the last GitHub server from Manage Jenkins should remove that server.
Actual Behavior
The user action to delete the last GitHub server does not change the configuration file. The last server will reappear the next time configuration is read, either by restart or by configuration reload.
Workaround
Edit the github-plugin-configuration.xml file and remove the last entry with a text editor.
dankirkd:
- Original comment link
Raw content of original comment:
markewaite - thanks for your added information. Unfortunately I cannot edit the github-plugin-configuration.xml file, so that's not a viable solution in my case.
markewaite - thanks for your added information. Unfortunately I cannot edit the github-plugin-configuration.xml file, so that's not a viable solution in my case.