-
Improvement
-
Resolution: Fixed
-
Major
Currently control files are generated in a subdirectory of the workspace. This is causing various issues because some build steps are not expecting these extra files which are internal to Jenkins.
These could be generated instead in a temporary directory or in a specific subfolder of the slave root instead.
- is duplicated by
-
JENKINS-30884 Workflow hangs on git clean after clone
-
- Resolved
-
-
JENKINS-32624 sshagent{} ignored when executed in docker.image().inside{...}
-
- Resolved
-
-
JENKINS-32943 withCredentials(FileBinding){} ignored when executed in docker.image().inside{...}
-
- Resolved
-
-
JENKINS-30240 Durable tasks fail with no message if tracking files accidentally deleted
-
- Resolved
-
- is related to
-
JENKINS-26105 Unkillable tasks
-
- Resolved
-
-
JENKINS-26133 Shell script taking/returning output/status
-
- Resolved
-
- relates to
-
JENKINS-60634 Define WORKSPACE_TMP=.../workspace/jobname@tmp
-
- Resolved
-
- links to
[JENKINS-27152] Store sh control files outside of workspace
Summary | Original: Store bourneshell control file outside of workspace | New: Store bourneshell control files outside of workspace |
Link |
New:
This issue is related to |
Remote Link | New: This issue links to "[jenkins-users] Workflow Plugin - Performing a Release (Web Link)" [ 12127 ] |
Link |
New:
This issue is related to |
Link |
New:
This issue is duplicated by |
Labels | Original: robustness workflow | New: api docker robustness workflow |
This is a very significant flaw with this plugin. The temporary-directory solution in the workspace is still far less than ideal, this really should use a system-provided temporary directory.