The TFS plugin currently allows excluding sources from given paths, however our source tree is very large and very active. New paths are added every day. The exclude / cloaking feature would allow us to exclude files / paths but if a new path is added then that path is pulled down in the next build even though it is not required. In our case it would be much more sensible to indicate to the TFS plugin which paths should be included and have it only get items from those paths.
Olivier Dagenais if you can provide me with some pointers I could have a crack at creating a pull request for this. I'd need to know where to look in the source code to make this happen.
I put in a PR in October 2017, that originally got merged but then pulled because of a failing test. I've put in this PR (https://github.com/jenkinsci/tfs-plugin/pull/196) last year and there has been no traction on it. We've been running the code in production but I don't have the time to keep chasing people to get it merged.
So in short, there is code, it's in my branch, it'll likely never get merged.
It seems the last release of any significance for the tfs-plugin was Mar 2018 (5.133.0). The 5.139.2 contained a one line fix and 5.157.0 contained an inaccurate documentation change to reflect the product's confusing new name. Is this Microsoft's way of telling us, go use GitHub ! ?