Obligatory link to Jenkins doc: https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds.
This sounds fairly straightforward for Jenkins. A Jenkins server can have any number of slave agents attached to it (I’ve personally run a server with 300+ agents and there are bigger ones out there), so you just put one slave agent on each host. Give each slave node the same label (like “remote”) and set up your jobs to require that label, and the jobs will only launch there (rather than on the master Jenkins server). If it only makes sense to run one thing on a box at a time, set the number of executors on the node to one; if not, set it to the maximum number of jobs you would feel comfortable running on that machine at a time. Each agent will reside on one machine, and they don’t talk to each other; all Jenkins communication goes through the server. If you have other questions, feel free to ask. If you need to know how to get the slave agents up and running on these machines, not what platform the slave machines are running. --Rob From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of ctime800 Sent: Friday, July 11, 2014 11:52 PM To: jenkinsci-users@googlegroups.com Subject: Jenkins setup question I need a Jenkins setup advise: What I want to achieve is like this: * Jenkins master 1 has: * Jenkins slave 1 * Jenkins slave 2 * Jenkins slave n Each slave will have identical software so that I can run the build/deploy job on each and load balancing them. All good with this setup so far? Then for deployment with an Agent (i.e. setting up Jenkins Agent in each slave to the runtime server for deployment), how do I achieve this goal with the above architecture? I think of the follow issue (not sure if they are): 1. The Jenkins slave cannot connect to another slave (the runtime server)? 2. How do slave 1 & slave 2 have the same Agent pointing to the same runtime server? If this is not the right approach, what will the new approach be? Again, what I want is to be able to add more slaves easily to support more loads when needed. I think the 'agentless' deployment model work, but agent deployment model will not work with this setup. Thanks for your help in advance! -- 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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>. For more options, visit https://groups.google.com/d/optout. Click here<https://www.mailcontrol.com/sr/jyKGat8RsOrGX2PQPOmvUqW!RI4xIDLr3j4LpY8DWDH4o24xPTWXmjvQ9CVHIG9Rz5IJDRCUVEZPpv0P1Tfw+Q==> to report this email as spam. ________________________________ This e-mail and the information, including any attachments it contains, are intended to be a confidential communication only to the person or entity to whom it is addressed and may contain information that is privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender and destroy the original message. Thank you. Please consider the environment before printing this email. -- 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/d/optout.
