[JIRA] (JENKINS-42973) User cannot create new Pipeline and locate it in a specific folder

0 views
Skip to first unread message

kshultz@cloudbees.com (JIRA)

unread,
Mar 21, 2017, 2:32:07 PM3/21/17
to jenkinsc...@googlegroups.com
Karl Shultz created an issue
 
Jenkins / Bug JENKINS-42973
User cannot create new Pipeline and locate it in a specific folder
Issue Type: Bug Bug
Assignee: James Dumay
Attachments: image-2017-03-21-14-30-32-279.png, image-2017-03-21-14-31-40-068.png
Components: blueocean-pipeline-editor-plugin
Created: 2017/Mar/21 6:31 PM
Environment: Client:
* Microsoft Windows 10 Professional, Microsoft Edge 38.14393.0.0
Jenkins:
* Core 2.32.3
* Blue Ocean 1.0.0-rc1
* Blue Ocean Pipeline Editor 0.2-rc1
Priority: Major Major
Reporter: Karl Shultz

Summary:
I have created, from within the Classic UI, a folder in which I can store my jobs. But when creating a new Pipeline from Blue Ocean, I don't see a way for me to store it there at creation time.

Steps to recreate:
1. From the classic UI, create a new folder. Name it anything you like:

2. Now from Blue Ocean, create a new Pipeline. Notice that there's no way to "locate" the new Pipeline in the folder you just created (or in any folder for that matter):

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

kshultz@cloudbees.com (JIRA)

unread,
Mar 21, 2017, 2:46:02 PM3/21/17
to jenkinsc...@googlegroups.com
Karl Shultz updated an issue
Change By: Karl Shultz
Component/s: blueocean-plugin
Component/s: blueocean-pipeline-editor-plugin

jdumay@cloudbees.com (JIRA)

unread,
Mar 21, 2017, 7:14:01 PM3/21/17
to jenkinsc...@googlegroups.com
James Dumay resolved as Not A Defect
 

Karl Shultz we've made the conscious decision to go for a different path than folders for organizing jobs in Blue Ocean. Folders encourage deep hierarchies of jobs which make it very difficult for users to discover their jobs (I can share some survey results if you are interested) and this is why browsing to a folder will not work in Blue Ocean nor is the usecase you have outlined in this ticket not supported.

Change By: James Dumay
Status: Open Resolved
Resolution: Not A Defect

kshultz@cloudbees.com (JIRA)

unread,
Mar 21, 2017, 8:12:01 PM3/21/17
to jenkinsc...@googlegroups.com
Karl Shultz commented on Bug JENKINS-42973
 
Re: User cannot create new Pipeline and locate it in a specific folder

James, thanks for the explanation, I appreciate that.

kshultz@cloudbees.com (JIRA)

unread,
Mar 21, 2017, 8:13:01 PM3/21/17
to jenkinsc...@googlegroups.com
Karl Shultz closed an issue as Not A Defect
 

As I just said above, this is a well-reasoned response, so I'll move this issue to a closed state.

Change By: Karl Shultz
Status: Resolved Closed

jdumay@cloudbees.com (JIRA)

unread,
Mar 21, 2017, 10:09:02 PM3/21/17
to jenkinsc...@googlegroups.com
James Dumay commented on Bug JENKINS-42973
 
Re: User cannot create new Pipeline and locate it in a specific folder

Karl Shultz thanks mate Really appreciate your team giving us a hand here!

matt.aizcorbe@gmail.com (JIRA)

unread,
Mar 6, 2018, 8:46:01 AM3/6/18
to jenkinsc...@googlegroups.com

I see this issue was closed and while I completely understand the logic behind the decision it creates an issue for those that are using the role-based access strategy.  We manage a Jenkins instance that serves many teams and we've created a scheme where we create a folder for each team and then create a role allowing access to that folder.  This gives each team their own workspace for managing jobs and credentials.  This scheme necessarily means that teams can't create jobs at the root level and thus they can't leverage this VERY useful capability.  We are huge advocates for the new pipeline method and want to lower the barrier of entry for those that are used to the point and click capability of freestyle jobs.  I haven't figured out another authorization scheme that is manageable given the number of teams we support.  I'd welcome any suggestions.

jonathan@jonathanfoster.io (JIRA)

unread,
Aug 14, 2019, 11:46:02 AM8/14/19
to jenkinsc...@googlegroups.com

James Dumay: I'm a huge fan of Blue Ocean. I'm coming to Jenkins from GitLab CI and I was really disappointed with the experience. That is until I came across Blue Ocean. Now I'm running into an issue though.

I have the same use case as Matt Aizcorbe, we use folders to isolate different teams and products. How can I use Blue Ocean with this structure? What's the different path you referred to above and is it functional?

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

wilkinsonjulian@gmail.com (JIRA)

unread,
May 6, 2020, 12:46:04 PM5/6/20
to jenkinsc...@googlegroups.com

Bump. The design doesn't account for organizations that use RBAC 

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages