-
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
jglick the bat 'cd .. && git clean -fdx' was required for previous versions where the control files were in the current working directory. The 1.8 update broke compatibility with that workaround because the control files moved from the CWD to the parent directory which moved them back to where they can't be. With version 1.8 the bat 'git clean -fdx' is what is needed now.
This incompatibility means that the change to the Jenkinsfile needs to be back-ported to all affected versions before they can build a new build successfully, however doing so immediately would trigger maintenance builds unnecessarily (Multi-Branch Pipeline Job) - which makes this incompatibility annoying.
And thanks for the long explanation!