Status: Resolved (View Workflow)
Resolution: Won't Fix
We use scripts to talk to Jenkins to administrate it. The scripts use a non-GitHub account (using the built-in User store in Jenkins). An example of this is the Jenkins Cookbook.
These scripts broke with github-oauth-plugin v0.26 because these users don't have GitHub accounts.
I know you just fixed all this, sag47 and I really appreciate your hard work on it.
I think what I would expect is that if someone used an SSH key or the API token that it falls back to the old behavior of not being in the github organizations.
I realize this is a little confusing for users; I can't think of any alternate ways to allow both GitHub users and non-GitHub users to work together.
- is related to
JENKINS-22346 CLI commands with private key for nonexistent user fail with EOFException from DataInputStream.readBoolean
- relates to
JENKINS-43822 Jenkins-cli seems to not support anything different from Github token
Yes. There is a system property to revert to the old behavior, which is considered a security hole.
Is there documentation for that property? I didn't see it on the security page(s) in the wiki.
I don't think it is what I want, but it'd be interesting to know.
It's working as designed which seems to be correct; closing this issue.
It's possible this was fixed by
Based on jglick's comment on
I suspect this isn't a bug, but rather a feature. JENKINS-22346