-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: All
In the Hudson tfs plug-in you only can configure the project path, whilst in
cruisecontrol.net you can configure path(s) that are excluded from this project
path when detecting modifications and checking out. For the CVS SCM plugni this
is already possible, it would be nice to also have this functionality in hudson.
For example: (cruise control.net configuration)
<sourcecontrol type="filtered">
<sourceControlProvider type="vsts" autoGetSource="true"
applyLabel="false">
<server>http://tfs_server:8080</server>
<username>username</username>
<password>***</password>
<domain>mydomain</domain>
<project>$/Content Manager/Main</project>
<workingDirectory>D:\CM</workingDirectory>
<cleanCopy>true</cleanCopy>
<workspace>workspace name</workspace>
<deleteWorkspace>false</deleteWorkspace>
</sourceControlProvider>
<exclusionFilters>
<pathFilter>
<pattern>$/Products/Main/Build/CruiseControl.NET/*/.*</pattern>
</pathFilter>
<pathFilter>
<pattern>$/Products/Main/Build/MasterBuild/*/.*</pattern>
</pathFilter>
<pathFilter>
<pattern>$/Products/Main/LegacyTest/*/.*</pattern>
</pathFilter>
<pathFilter>
<pattern>$/Products/Main/Documentation/*/.*</pattern>
</pathFilter>
<pathFilter>
<pattern>$/Products/Main/Source/FunctionalTests/*/.*</pattern>
</pathFilter>
<pathFilter>
<pattern>$/Products/Main/Source/Tools/Debug
Clients/*/.*</pattern>
</pathFilter>
<pathFilter>
<pattern>$/Products/Main/Source/Tools/Test
Clients/*/.*</pattern>
</pathFilter>
<pathFilter>
<pattern>$/Products/Main/Source/Tools/Misc/*/.*</pattern>
</pathFilter>
</exclusionFilters>
</sourcecontrol>
[JENKINS-4709] Add exclusion regions in TFS polling and checkout
Brett Rogers
added a comment - Any idea when Mike's pull request might be addressed? We could really use this functionality.
Brett Rogers
added a comment - Any idea when Mike's pull request might be addressed? We could really use this functionality. 
qing dai
added a comment - anyway to fasten the process of release of TFS plugin? 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
This should be pretty simple to implement. Let me know if there are other questions about TFS SCM.
Kyle O'Connor
added a comment - - edited 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
This should be pretty simple to implement. Let me know if there are other questions about TFS SCM. 
Aaron Alexander
added a comment - There is a new pull request (https://github.com/jenkinsci/tfs-plugin/pull/28) that implements this with workspace cloaking.
Aaron Alexander
added a comment - There is a new pull request ( https://github.com/jenkinsci/tfs-plugin/pull/28 ) that implements this with workspace cloaking. In the table at the bottom of this page it says that the TFS plugin v4.1.0 does NOT support authentication.
Couple of questions:
1. When will authentication be supported?
2. How are proxies supported by 4.1.0 if authentication isn't?
Kellie Jos
added a comment - Closing this issue as TFS plugin v5.1.0 introduced support. 
Added a pull request for basic exclusion region support based off the SVN implementation:
https://github.com/hokatichenci/tfs-plugin/commit/6e7afd9b665560258a2689ee15e72f1a73ac5e52