ExecutorStep adds a WorkspaceAction to track the fact that the flow build used a workspace, and if you navigate the flow graph UI you can get to a workspace browser, but there is not much more than that available. Need:

      • Analogue of noWorkspace.jelly in case a workspace cannot be loaded
      • Nicer DirectoryBrowserSupport.title: WorkflowRun.getFullDisplayName, computer, path, ...
      • Functionality similar to doDoWipeOutWorkspace, though see JENKINS-4646 and related issues
      • FlowNodeViewColumn or other way of seeing a list of workspaces for a build (or for the last build of the project)

          [JENKINS-26138] Support workspaces for Pipeline jobs

          Jesse Glick created issue -
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-4646 [ JENKINS-4646 ]

          I assume that this ticket also covers the "Oops" when one navigates to a workspace on a slave that's currently off-line (e.g. http://localhost:8080/job/MyWorkflow/3/execution/node/3/ws/ )? A friendlier error message, with slave name etc, would be good. However, a direct link to the slave node would be better, and a REST api would be best.

          Thomas Goeppel added a comment - I assume that this ticket also covers the "Oops" when one navigates to a workspace on a slave that's currently off-line (e.g. http://localhost:8080/job/MyWorkflow/3/execution/node/3/ws/ )? A friendlier error message, with slave name etc, would be good. However, a direct link to the slave node would be better, and a REST api would be best.

          Jesse Glick added a comment -

          Currently a 404 is served when the workspace is unavailable. I was not aware this renders using oops.jelly; if so, that is a mistake. Anyway the first item covers replacing this with noWorkspace.jelly.

          Jesse Glick added a comment - Currently a 404 is served when the workspace is unavailable. I was not aware this renders using oops.jelly ; if so, that is a mistake. Anyway the first item covers replacing this with noWorkspace.jelly .
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-26432 [ JENKINS-26432 ]

          Anders Hammar added a comment -

          If the flow graph UI isn't available in the OSS version there needs to be some other way to manage the workspace, e.g. delete it.

          Anders Hammar added a comment - If the flow graph UI isn't available in the OSS version there needs to be some other way to manage the workspace, e.g. delete it.

          Jesse Glick added a comment -

          The flow graph is present in the workflow-job plugin. But deleting the workspace is not yet implemented, as already noted here (third item).

          Jesse Glick added a comment - The flow graph is present in the workflow-job plugin. But deleting the workspace is not yet implemented, as already noted here (third item).
          Jesse Glick made changes -
          Link New: This issue is duplicated by JENKINS-28382 [ JENKINS-28382 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-30346 [ JENKINS-30346 ]

          Jesse Glick added a comment -

          SCM.processWorkspaceBeforeDeletion should also be checked during

          WorkspaceListener could also be fired if it were updated to grok Job.

          WorkspaceCleanupThread also needs editing.

          Jesse Glick added a comment - SCM.processWorkspaceBeforeDeletion should also be checked during DeleteDirStep ( JENKINS-30346 ) WorkflowJob.performDelete WorkspaceListener could also be fired if it were updated to grok Job . WorkspaceCleanupThread also needs editing.
          Jesse Glick made changes -
          Link New: This issue is blocking JENKINS-30346 [ JENKINS-30346 ]

            jglick Jesse Glick
            jglick Jesse Glick
            Votes:
            112 Vote for this issue
            Watchers:
            125 Start watching this issue

              Created:
              Updated: