TFS Plugin - different location between master and slave

Raj

unread,

Mar 13, 2012, 5:14:26 PM3/13/12

to Jenkins Users

We have our Jenkins master on linux with the [Team Foundation Server -
TF commandline executable] parameter set to /opt/TEE-CLC-10.1.0/tf.
Our 'windows' slave has Visual Studio installed. The build fails on
the slave because the /opt/TEE-.../tf tfs client is being called
instead of the one included in Visual Studio. I see no way of setting
a different path for this tool on the 'windows' slave.

Can the master and slave have different paths to their TFS tools as is
configurable for Java,Maven and MSBuild?

Raj

unread,

Mar 13, 2012, 5:14:26 PM3/13/12

to Jenkins Users

Erik Ramfelt

unread,

Mar 14, 2012, 10:45:38 AM3/14/12

to jenkins...@googlegroups.com

If you add the tfs path to the PATH env variable on the machines then you can have different locations of the tfs tool. In Jenkins then you just configure 'tf' as the tool path.

Would that work?

Regards Erik

Raj

unread,

Mar 14, 2012, 11:02:11 AM3/14/12

to Jenkins Users

Thanks Erik. That worked great. I had to bounce both the master and
slave for the path change to be picked up.

-Raj

On Mar 14, 8:45 am, Erik Ramfelt <eramf...@gmail.com> wrote:
> If you add the tfs path to the PATH env variable on the machines then you
> can have different locations of the tfs tool. In Jenkins then you just
> configure 'tf' as the tool path.
>
> Would that work?
>
> Regards Erik

Reply all

Reply to author

Forward