-
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
Code changed in jenkins
User: Oleg Nenashev
Path:
README.md
docs/logging.md
docs/workDir.md
src/main/java/hudson/remoting/Engine.java
src/main/java/hudson/remoting/FileSystemJarCache.java
src/main/java/hudson/remoting/Launcher.java
src/main/java/hudson/remoting/TeeOutputStream.java
src/main/java/hudson/remoting/jnlp/Main.java
src/main/java/org/jenkinsci/remoting/engine/WorkDirManager.java
src/test/java/org/jenkinsci/remoting/engine/WorkDirManagerTest.java
http://jenkins-ci.org/commit/remoting/76c9b8ccf14f7def1141565b0dee2e4d1c5508d4
Log:
[JENKINS-39370,JENKINS-39369] - Support of work directories in Remoting (#129)
JENKINS-39370- Generalize the workspace manager for Java Web StartJENKINS-39370- WiP - Save progress in the test suiteJENKINS-39370- Add tests for WorkDirManagerJENKINS-39370- Restrict the range of supported symbols in the remoting work directoryJENKINS-39370- Generalize the workspace initialization checksJENKINS-39130- Allow specifying flag for failing initialization if workdir is missingJENKINS-39370- Reference DirType in WorkDirManager JavadocsJENKINS-39370- @stephenc noticed that workDir may be null, Intellij IDEA adoption funJENKINS-39370- Seems this message breaks our CIJENKINS-39370- Another message, which likely breaks the CI instanceJENKINS-39370- Simplify the log handling logicJENKINS-39817- Introduce the agentLog parameter in remoting.jnlp.Main@stephenc suggested doing it in the PR, so I decided to address it as a part of
JENKINS-39370.But the code still has initialization in hudson.remoting.Launcher for other logging modes.
JENKINS-18578- If workspace manager is defined, use JAR Cache within its interbal directoryJENKINS-39370- Fix the workDirManager's log initialization in LauncherJENKINS-39370- Draft the documentationJENKINS-39369- Make JUL logging system configurable via property fileJENKINS-39369- Fixes in logging management after the manual testingJENKINS-39369- Add tests for the logging subsystemJENKINS-39369- Respect configuration being passed from java.util.logging.config.file system property