-
Task
-
Resolution: Fixed
-
Critical
-
-
1.0-japan-m9, 1.0-m10
When items are shown on the main dashboard (/pipelines) they may include items that are from nested folders.
When clicking on an item that is in a folder, it needs to be loaded with the URI reflecting what its folder path is.
In Scope
- When UX-276 is completed we need to handle nested folder jobs in the frontend
- Always use the fullName as the display name
- Browsing to a pipeline should work if its in a folder
- Browsing to a folder should 404
Browsing to a folder just show a list of the folder contents as if that folder was the "root" of the dashboard
[1:24 PM] James Dumay: e.g if I browse to /org/my/sub/folder/
[1:24 PM] James Dumay: show everything under /org/my/sub/folder/ as it is "/"
- is blocked by
-
-
- Resolved
-
[JENKINS-35866] Handle jobs that are stored within folders
jdumay this will involve the design as per the mockups in https://cloudbees.atlassian.net/browse/UX-196 right?
mnealeAs mentioned in comment in https://cloudbees.atlassian.net/browse/UX-196, "There is issue of how to detect folder vs pipeline, that gets addressed with data extensibility/capability work.", this is cross cutting concern and going to be addressed in UX-68/UX-350.
vpandey actually can use the numOfFolders etc to know if something is a folder at least (so they can not be shown at top level).
cmeyers sorry I may have mislead this morning when talking through URIs.
The aim is that the main dashboard does show (paginated) all pipelines from all folders (but not the folders themselves). This is a big long flat list. When we have that, we will need to be able to let the user click on something that is in a folder (even though it is flattened out on the main dashboard) and have it load, with the correct data URL for rest, and the URI in the browser set correctly - which is what this ticket is about.
cliffmeyers here is the whiteboard where we talked about where to put the path:
I am not sure if tscherler was also attacking this - I don't think so.
Yes, this is in-progress. I was in training on Wed, but had time to squash a few small bugs during breaks. I plan to focus on this on Thu.
So if we look at the REST url:
https://github.com/jenkinsci/blueocean-plugin/tree/master/blueocean-rest#get-nested-pipeline-inside-a-folder
http://localhost:62054/jenkins/blue/rest/organizations/jenkins/pipelines/folder1/pipelines/folder2/test2/
breaking it down:
so "pipelines" acts as a separator