I don't think the patch based on the SVN impl is the way to go. This needs to be implemented using TFS "cloaking". See here: http://msdn.microsoft.com/en-us/library/ms181378(v=vs.100).aspx

The Jenkins TFS SCM plugin configuration page should simply ask for a list of folders (TFS Server paths) you want to be excluded from the SCM checkout and then run the tf workfold /cloak command on this folder list. It only has to be run once when the workspace is initially created (unless the configuration changes, but since this plugin already supports recreating the workspace in that case, you would also just make the call to cloak all folders again at that point). See here for the command syntax: http://msdn.microsoft.com/en-us/library/0fa04bx6(v=vs.100).aspx

Let me know if there are other questions about TFS SCM.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to