Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-49354

unable to configure private GitHub repository with collaborator token

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None

      Steps to reproduce

      1) as User A, create a private repository on github

      2) give access to it to User B (Add collaborator)

      3) try to configure Jenkins access using blue ocean create pipeline (/blue/organizations/jenkins/create-pipeline) using User B token

       

      Expected result:

      I'm able to select all repositories User B has access to, including private repository of User A that User B has been granted permission to.

       

      Current result:

      I'm forced to choose organization "Which organization does the repository belong to?"

      and only user B (token owner) is listed.

       

      In the mean time I have used similar workaround to one from JENKINS-37359 , but it has to be redone every time I use web UI to change the configuration as it renders the repository name value inside a <select> which does not have that option display, resulting in selecting first public repository instead.

      Redacted screenshot representing this particular problem:

       

      It may be required to split this issue into two - one for blue ocean and one for github plugin.

            lanwen Kirill Merkushev
            rooter Maciej Urbański
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: