-
New Feature
-
Resolution: Fixed
-
Major
-
None
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
- 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
[JENKINS-39370] Introduce the remoting working directory concept
Epic Link | New: JENKINS-38833 [ 175240 ] |
Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Link |
New:
This issue blocks |
Link |
New:
This issue blocks |
Description |
Original:
Right now remoting has no it's own Working Directory on startup. It complicates implementation of features like |
New:
Right now remoting has no it's own Working Directory on startup. It complicates implementation of features like 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 |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Link |
New:
This issue is blocking |
Comment | [ Oleg, you've marked this as In Review, but none of the issues link to any PR. ] |