This was very helpful. I used this guide to help clarify that:
Username is the GitHub user ID and Password is the Password or a personal API Token (recommended).
The contextual in-line help (and gitScm pipeline step error handling) don't mention that a pure 'Secret Text' API Token cannot be used without the username.
Effectively, Github use in Jenkins requires a Github service account to be managed by operations/IT.
Comments
2 comments
This was very helpful. I used this guide to help clarify that:
Username
is the GitHub user ID andPassword
is the Password or a personal API Token (recommended).The contextual in-line help (and gitScm pipeline step error handling) don't mention that a pure 'Secret Text' API Token cannot be used without the username.
Effectively, Github use in Jenkins requires a Github service account to be managed by operations/IT.
Thanks @john hill
Please sign in to leave a comment.