-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Linux
I upgraded to Jenkins 1.456 today, and now my jobs that use the Clone Workspace plugin are having problems because the workspace tar.gz that is created when the job completes no longer includes the .git directory. In 1.449, which I ended up downgrading back to, the default setting for files to include always pulls that in. I've verified this by running tar -tzf on the workspace.tar.gz; in 1.449 .git is there, in 1.456 it isn't.
I wasn't able to force Jenkins to include it either. I tried putting "**/, **/.git" and other variations on that in the list of files to include, but none of them seemed to work.
- is related to
-
JENKINS-13888 Please override new Ant default excludes when cloning workspaces, so .git/.gitignore and other files are not lost during cloning
-
- Resolved
-
-
JENKINS-14900 Copying from workspace drops files matching Ant's default excludes
-
- Closed
-
-
JENKINS-14355 Allow disabling use of default exclude patterns (.git, .svn, etc.) for fingerprinting
-
- Open
-
-
JENKINS-7999 Add a way to override "default excludes"
-
- Closed
-
For the records: Since Ant 1.8.2, Git files/directories (and those of other SCMs) are included in the "default excludes", which is why the files are lost in a cloned workspace. Therefore this is not a Jenkins "bug" but an Ant "feature". I have opened a pull request allowing the disabling of those default excludes. Plugins like Clone Workspace may use this to let Git files reappear.