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

Cannot browse workspaces of jobs using the cloudbees-folder-plugin

    Details

    • Similar Issues:

      Description

      MappedFsWorkspaceBrowser uses this to calculate the workspace directory of a job:

      new FilePath(getFile(new File(action.remoteFsMapping), "workspace", job.getName()))
      

      This works fine for toplevel jobs, but not for jobs whose directory is one or more sub directories below the "workspace" directory.

        Attachments

          Issue Links

            Activity

            Hide
            capf Carsten Pfeiffer added a comment -

            Here's the link to the pull request: https://github.com/jenkinsci/docker-plugin/pull/473

            Show
            capf Carsten Pfeiffer added a comment - Here's the link to the pull request: https://github.com/jenkinsci/docker-plugin/pull/473
            Hide
            aamerik Alexey Amerik added a comment - - edited

            This issue was a real time sink for us. Thank you very much for filing this bug and for the PR! Hoping for this to get merged quickly.

            Show
            aamerik Alexey Amerik added a comment - - edited This issue was a real time sink for us. Thank you very much for filing this bug and for the PR! Hoping for this to get merged quickly.
            Hide
            capf Carsten Pfeiffer added a comment -

            Any update on this? Should we ping someone else to get this merged? There's also JENKINS-36919 with a useful patch waiting to get merged.

            Show
            capf Carsten Pfeiffer added a comment - Any update on this? Should we ping someone else to get this merged? There's also JENKINS-36919 with a useful patch waiting to get merged.
            Hide
            ndeloof Nicolas De Loof added a comment -

            PR #473 is far from being enough to get this feature working correctly. 

            This mechanism assumes a local docker daemon, a better approach would be to use a volume and run a temporary container with this volume for file browsing.

            So this is a larger issue

            Show
            ndeloof Nicolas De Loof added a comment - PR #473 is far from being enough to get this feature working correctly.  This mechanism assumes a local docker daemon, a better approach would be to use a volume and run a temporary container with this volume for file browsing. So this is a larger issue

              People

              • Assignee:
                ndeloof Nicolas De Loof
                Reporter:
                capf Carsten Pfeiffer
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: