[ 
https://issues.jenkins-ci.org/browse/JENKINS-13888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163173#comment-163173
 ] 

SCM/JIRA link daemon commented on JENKINS-13888:
------------------------------------------------

Code changed in jenkins
User: Andrew Bayer
Path:
 pom.xml
 src/main/java/hudson/plugins/cloneworkspace/CloneWorkspacePublisher.java
 
src/main/resources/hudson/plugins/cloneworkspace/CloneWorkspacePublisher/config.jelly
 src/test/java/hudson/plugins/cloneworkspace/CloneWorkspaceSCMTest.java
http://jenkins-ci.org/commit/jenkins-clone-workspace-scm-plugin/0bfecdad2fddc44c43b96f88ed373ab225e330e6
Log:
  [FIXED JENKINS-13888] Add option to turn off default Ant excludes from 
workspace archive.





                
> Please override new Ant default excludes when cloning workspaces, so 
> .git/.gitignore and other files are not lost during cloning
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13888
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13888
>             Project: Jenkins
>          Issue Type: Bug
>          Components: clone-workspace-scm
>    Affects Versions: current
>         Environment: Linux, Jenkins 1.465
>            Reporter: owenmehegan
>            Assignee: abayer
>
> The fix for JENKINS-13165 seems to have been to create a hook that plugins 
> can use to *optionally* override the new (@#$!@$) Ant default excludes, which 
> now include .git/.gitignore, etc. I would like for the Clone Workspace plugin 
> to override these defaults, or at least give me a check box to do that.
> To reproduce the problem, create a job which touches a file named .gitignore, 
> and publish that job's workspace for archiving. Then create another job which 
> pulls over that archive and does an 'ls -la' in it. The .gitignore file won't 
> be there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to