Master/Slave requirements

[jer...@bodycad.com]

Hi,

I would like to know how people are doing to manage the slave requirements and installation when having different platform between master and slave.

I'm currently having a very simple setup where my Windows master have everything installed on it and no slave.  We are looking at making a Linux Master and Windows slaves.

• Linux Master
• many Windows slaves
• different Visual Studio version on slaves
  
• I already use Jenkinsfile pipeline, may need to adjust some node stuff

Is it possible to have groovy/python scripts on the master accessible by the salve:

1. do I need to stash them and unstash them at every build?
   
2. can I access them directly on the salve by requesting the master?

Is Jenkins plugins on the master accessible on the salves? timestamps, zip util, email ...

How one give installed software on the salve or manage them? especially the one not handled by Jenkins like Microsoft Visual Studio.

Can I force to have them and keep the installer or archive to deploy them on the slave machine (like Python 2.7, Doxygen)?

I also have some lint executable for Windows only, can I store them on the Master and deploy them on slvae automaticaly or I need to setup each slave manually?

If someone can shed some light on this, I will begin the migration testing later this week, but would like to have a better idea before I take a plunge into this and not try stuff that are impossible.

Thanks,

Jerome