As Jenkins now actually embeds jetty, I would say go the simplest way: start with java -jar Jenkins.war (10+ slaves).
But it also depends what you're used to, sure. For example, if you have good internal experience operating tomcat, running Jenkins inside tomcat would certainly still be a sensible choice for you. Cheers Le 18 mars 2014 08:50, "Kake" <[email protected]> a écrit : > Hi > > > > I'm in the process of migrating some Jenkins installations from old 2003 > servers to some newer ones. > > The old setup uses jetty and some intricate java wrapper to start each > instance. > > > > I.e. the Jetty home is installed on one “location” and the Jenkins home > directory is located in a different folder/dir. There is a one-one ratio > between the jetty “installs” and the Jenkins instances. > > > > Setup: 5+ Jenkins Instances, each instance 20- 50 jobs. (win 2008 server) > > > > Question: What’s the “best practices” when configuring such an > environment, use container or not? > > -- > 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/d/optout. > -- 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/d/optout.
