Skip to main content

GitHub Permissions and API token Scopes for Jenkins

Comments

2 comments

  • John Hill

    This was very helpful. I used this guide to help clarify that:

    Username is the GitHub user ID and Password is the Password orpersonal 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

    Thanks @john hill

    0

Please sign in to leave a comment.

About CloudBees Support

Our Support Engineers are available to help with any questions or problems you may have with any of our products.