[JENKINS-26138] Support workspaces for Pipeline jobs

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

---
Originally reported by jglick, imported from: Support workspaces for Pipeline jobs

• assignee: jglick
  
• status: In Review
  
• priority: Major
  
• component(s): workflow-support-plugin
  
• resolution: Unresolved
  
• votes: 112
  
• watchers: 125
  
• imported: 20260601-173816
  

Raw content of original issue

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)