On Thu, Jun 5, 2014 at 2:12 PM, Kohsuke Kawaguchi <[email protected]> wrote: > I started "java -jar jenkins.war" just as a convenience, > but […] more than 80% of the installation base is running on this container > today.
FYI, many of the large companies CloudBees has a support customers run Jenkins via native packages, typically RPM, and these use the built-in container. So making it fast by default is definitely laudable. As to mismatch with hpi:run, this is definitely a concern—although there is no reason hpi:run (and hudson-dev:run, used by jenkinsci/jenkins/war) could not be switched to Undertow as well, especially if it started a bit faster. Generally speaking we ought to be running acceptance tests in a variety of containers to catch container-specific problems: at least Jetty, Undertow, and Tomcat, and at least during LTS RC testing (may be too expensive to do more often than that). -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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.
