GitHub Permissions and API token Scopes for Jenkins Bee Bot July 13, 2022 11:02 Updated The content of this article has moved to the new documentation site. Related articles GitHub Integration: Webhooks How to Customize Checkout for Pipeline Multibranch? GitHub: How to configure status checks per Pipeline stage for Pull Requests How can I purge/clean the build queue? How to troubleshoot 'hudson.FilePath is missing' in a Pipeline run Comments 2 comments Sort by Date Votes John Hill January 18, 2018 20:21 Edited 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. 0 Carlos Rodriguez Lopez March 25, 2020 17:39 Thanks @john hill 0 Please sign in to leave a comment.