HI - I need some advice on organizing the nodes. Running Jenkins ver. 1.509.2 on linux VMs, we have a master and 4 slaves.
Previously the slaves were only used to run long-running automated testing but we are finding we need more executors for deploys. I thought I would keep the builds limited to just the master node so that the artifacts would all be retained in one location. We often have to refer back to previous builds and I am assuming that if a build can run on any node, its associated artifacts would only be found on that node. Is that a correct assumption? Conversely I suppose we could tie certain builds to certain nodes and maintain their archives there. The drawback with tying certain types of jobs to certain nodes is the additional requirement to apply the label to each job. This may be an annoyance as we roll out jenkins access to all the developers. What kind of setup have you found to work best in your organization? -- 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.
