On Sun, Feb 24, 2013 at 4:27 AM, Syed Mahdi <[email protected]> wrote: > > > (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?
Jobs running on the master will all run under the same user id. > 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. I don't think there is any real difference in functionality. If you only have one platform. > 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 ). Slaves on the same machine would let you have different user ids and workspace areas but would still build the same things. > Appreciate any insight from people who have run slaves and if they can tell > me how it benefited them. The big win is if you build for different platforms or need more capacity than a single machine. And because jenkins handles remoting so well it is not a big problem if you want to run slave instances on the master machine. -- Les Mikesell [email protected] -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
