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

Handle jobs that are stored within folders

    Details

    • Epic Link:
    • Sprint:
      1.0-japan-m9, 1.0-m10
    • Similar Issues:

      Description

      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 "/"

        Attachments

          Issue Links

            Activity

            Hide
            michaelneale Michael Neale added a comment -

            Doesn't make sense to tackle this without fixing up the URIs

            Show
            michaelneale Michael Neale added a comment - Doesn't make sense to tackle this without fixing up the URIs
            Hide
            michaelneale Michael Neale added a comment -

            [~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.

            Show
            michaelneale Michael Neale added a comment - [~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.
            Hide
            michaelneale Michael Neale added a comment -

            Cliff Meyers here is the whiteboard where we talked about where to put the path:

            I am not sure if Thorsten Scherler was also attacking this - I don't think so.

            Show
            michaelneale Michael Neale added a comment - Cliff Meyers here is the whiteboard where we talked about where to put the path: I am not sure if Thorsten Scherler was also attacking this - I don't think so.
            Hide
            cliffmeyers Cliff Meyers added a comment -

            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.

            Show
            cliffmeyers Cliff Meyers added a comment - 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.
            Show
            cliffmeyers Cliff Meyers added a comment - PR: https://github.com/jenkinsci/blueocean-plugin/pull/299

              People

              • Assignee:
                cliffmeyers Cliff Meyers
                Reporter:
                jamesdumay James Dumay
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: