The procedures in this chapter are for new installations of Jenkins.
Jenkins is typically run as a standalone application in its own process. The Jenkins WAR file bundles Winstone, a Jetty servlet container wrapper, and can be started on any operating system or platform with a version of Java supported by Jenkins.
Theoretically, Jenkins can also be run as a servlet in a traditional servlet container like Apache Tomcat or WildFly, but in practice this is largely untested and there are many caveats. In particular, support for WebSocket agents is only implemented for the Jetty servlet container. See the Servlet Container Support Policy page for details.
The Jenkins project produces two release lines with difference cadences or frequencies. One once about every 4 weeks, and one weekly. Choose one before installing, because the installation instructions and packages differ between them.
An LTS baseline is chosen every 12 weeks from the stream of weekly releases. Every 4 weeks, a new LTS release delivers backported bug and security fixes. This line changes less often and suits more conservative users. See LTS Release Line for how baselines are chosen and fixes are backported.
The weekly line delivers bug fixes and new features rapidly to users and plugin developers who need them, generally on a weekly cadence. See Weekly Release Line.
Each release line has its own changelog respectively: LTS changelog and weekly changelog. To move an existing installation from one line to the other, see the instructions at Switching Between Release Lines.
Please submit your feedback about this page through this quick form.
Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?
See existing feedback here.