Hi Nelson, It sounds like you are running into some of the limitations of GitHub organizations that others have faced as well. In the past couple of weeks, the Blue Ocean team has landed some changes so that new GitHub-based pipelines are created as Multibranch Pipelines instead. Once this ships, any new pipeline you create should be able to be configured in a much more flexible way. If you're curious, the PR that included these changes is here: https://github.com/jenkinsci/blueocean-plugin/pull/1336
These changes will be available in the next beta release of Blue Ocean which should ship in a week or two to the experimental update center. Or you can wait for the production 1.3 release, although I can't say with certainty when that will ship. In the mean time, if you want to control which repositories in your GitHub org are built, in the Classic UI you can click on the "Configure" link on the left and then find the "Filter by name (with regular expression)" section. That regex should reflect all of the repository names you selected via the Blue Ocean "New Pipeline" UI. If you remove entries and press "Save" it will add or remove the child pipelines accordingly. If you have more questions feel free to post here and I'll do my best to help. -Cliff On Sun, Sep 3, 2017 at 9:55 PM, Nelson Liu <[email protected]> wrote: > Hi! > I've been trying out BlueOcean for managing my CI projects---it's great! > I'm able to create a new pipeline and specify that I want to pull code from > a repo in my Github organization, and the builds run beautifully. However, > it doesn't seem like I (as an administrator user on the Jenkins instance) > have any sort of permissions on the repository projects. > > For example, I'm able to modify the settings of and delete the Github > organization folder created by BlueOcean, but I can't seem to modify the > settings of or delete the repositories that I've added from the > organization. I'm also unable to modify the configuration of the individual > branches in the repository. > > Security is enabled, and I'm using Jenkins' own database. In terms of > authorization, I've specified that logged-in users can do anything and I've > verified that I'm actually logged in when I try the above. > > Any pointers on what I could be doing wrong, or is it intended that users > are not able to modify the configuration of individual repositories / > branches? > > Thanks! > Nelson Liu > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-users/39df2145-eb5c-45a0-9340-085c1649c7ae%40googlegroups. > com > <https://groups.google.com/d/msgid/jenkinsci-users/39df2145-eb5c-45a0-9340-085c1649c7ae%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAFm%3D0hez2JmfZ%3D%2BAgmhXAvDvQxAvRARGmEq11OPivi_MAFp9Sw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
