Details
-
Type:
New Feature
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: remoting
-
Labels:None
-
Similar Issues:
-
Epic Link:
Description
Right now remoting has no it's own Working Directory on startup. It complicates implementation of features like JENKINS-39369 and JENKINS-18578
Requirements:
- The directory is compatible with the current agent workspace architecture of JNLP slaves and
- The directory is being created only if explicitly required (behavior compatibility for the current workspace-less agents)
- The workspace should not interfere with Jenkins plugins putting the data to the root of the agent workspace
Attachments
Issue Links
- blocks
-
JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars
-
- Resolved
-
-
JENKINS-39369 Automatically dump agent logs to the disk
-
- Resolved
-
- is blocking
-
JENKINS-39130 Jenkins JNLP agents should not connect/schedule builds if the workspace cannot be created or not writable
-
- Resolved
-
- links to
Merged towards Jenkins 2.68