How is the TFS plugin supposed to checkout sources on remote nodes

[Andy Falanga]

I've updated my TFS plugin to 4.0.0 (the latest).  Jenkins is running on a Windows system.  I must build in Linux.  We have 3 systems configured as slave nodes for this purpose.  The project that I configured in Jenkins did farm the job to one of the correct slave nodes.  However, although the build log shows that all of the TFS workspaces (rather irritating that this term is overloaded) were listed, it doesn't show that any sources were checked out. 

I scrapped my old project because it just wasn't working correctly.  I made a "free-style software project" and put in the settings necessary to check out code from my branch in TFS.  How is this normal flow supposed to work?  Am I going to have to use the TEE client on the slave nodes?  If so, I thought that version 4.0.0 of the TFS plugin was supposed to mitigate this?  It claims to at least.  I'd appreciate knowing how this is supposed to work with remote nodes.

Thanks for any help.

[Stefan Drissen]

I would steer away from the 4.0.0 plug-in until it is more stable.

1. a job created with 3.2.0 plugin will simply fail with 4.0.0 plugin - see https://issues.jenkins-ci.org/browse/JENKINS-30355
   
2. list workspaces lists all workspaces on all servers - see https://issues.jenkins-ci.org/browse/JENKINS-30330
   
3. (windows) slaves have been giving all sorts of NumberFormatExceptions - https://issues.jenkins-ci.org/browse/JENKINS-30382
   

Since installing 4.0.0 slaves were crashing frequently. On the windows slaves I uninstalled the TFS clients (VS Team Explorer) and the get latest was /generally/ working but often resulting in an unsatisified link error.

Everything was (and now is again) working quite nicely with 3.2.0. On my one Linux slave the TEE client is installed.