- 
    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
