Hello All, I am new to jenkins space. I was wondering why would i need master and slaves. We have some applications that are going to be built and deployed through jenkins jobs. currently there is one for three different environments. Why would i need slaves in the setup. I have one master, i can configure # of executors on the Master to be 10, so ten parallel jobs can be run. Will this have any problems. I can setup all the jobs in the master to be run. i dont think there will ever be more than three jobs running at the same time, even for the rest of the applications. So do i need a slave.if slaves are only there to build in parallel then what is the difference with # of executors.
(I am under the impression that slaves are only job running machines so the configuration lies only in Master. So if that is not true, also, if i configure the security in jenkins, Will the jobs running on slaves be visible to some other users or can i control which user can access which slave or can i control which user can see which job? You can see I am confused myself. My setup would be like 5 applications only two of them have very frequent changes so two applications will have at least 1 or 2 builds everyday. 1 application will have at max one build per week and another 2 applications with only one build per two weeks. Confusing me more is the concept of having a slave on the same machine which is an optional possibility. Then what is the slave doing when there is already a master. (I was reading this : https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds ). Appreciate any insight from people who have run slaves and if they can tell me how it benefited them. Thanks. Syed Mahdi -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.