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

[UX] Not clear how to add a new github project if organizations already exist

XMLWordPrintable

      When adding a new pipeline based on a different github account, it's not immediately apparent that the 'git' flow needs to be followed instead of 'github'.

      Precondition:

      1. Existing Github Organizations and Pipelines
        1. i.e. organization "A" with repos "A1, A2, A3"

      Steps to reproduce:

      1. Attempt to add a new pipeline in blue ocean
        1. i.e. organization "C" with repo "C1" 
        2. Click on 'Github' button under 'Where do you store your code?'
        3. Navigated to 'In which Github organization are your repos located?'

      It seems that the current flow does not allow the user to add a new github rep pipeline if an organization isn't already added.

       

        1. Screen Shot 2017-03-20 at 1.54.52 PM.png
          Screen Shot 2017-03-20 at 1.54.52 PM.png
          101 kB

          [JENKINS-42984] [UX] Not clear how to add a new github project if organizations already exist

          James Dumay added a comment - - edited

          jhill I suspect this is a misunderstanding - you can only use this flow to connect to Github organizations or accounts that you are a member of. What you see in that list does not have anything to do with the organization folders created on Jenkins.

          For example:

          • Alice and Bob are members of the Widgets Co. organization on Github.
          • Alice is presented in creation options to create her repository from "Alice" and "Widgets Co."
          • Bob is presented in creation options to create his repository from "Bob" and "Widgets Co."
          • Alice cannot create a repository from "Bob" - they would have to use the "Git" option to do this.
          • Bob cannot create a repository from "Alice" - they would have to use the "Git" option to do this.
          • Neither Alice and Bob can create a repository from "Super Great JS project" that contains a bunch of OSS repositories with anon access. They would have to use the "Git" option to do this.

          James Dumay added a comment - - edited jhill I suspect this is a misunderstanding - you can only use this flow to connect to Github organizations or accounts that you are a member of. What you see in that list does not have anything to do with the organization folders created on Jenkins. For example: Alice and Bob are members of the Widgets Co. organization on Github. Alice is presented in creation options to create her repository from "Alice" and "Widgets Co." Bob is presented in creation options to create his repository from "Bob" and "Widgets Co." Alice cannot create a repository from "Bob" - they would have to use the "Git" option to do this. Bob cannot create a repository from "Alice" - they would have to use the "Git" option to do this. Neither Alice and Bob can create a repository from "Super Great JS project" that contains a bunch of OSS repositories with anon access. They would have to use the "Git" option to do this.

            Unassigned Unassigned
            jhill John Hill
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: