Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Easy installation: Just run java -jar jenkins.war, deploy it in a servlet container. No additional install, no database. Prefer an installer or native package? We have those as well.
  2. Easy configuration: Jenkins can be configured entirely from its friendly web GUI with extensive on-the-fly error checks and inline help.
  3. Rich plugin ecosystem: Jenkins integrates with virtually every SCM or build tool that exists. View plugins.
  4. Extensibility: Most parts of Jenkins can be extended and modified, and it's easy to create new Jenkins plugins. This allows you to customize Jenkins to your needs.
  5. Distributed builds: Jenkins can distribute build/test loads to multiple computers with different operating systems. Building software for OS X, Linux, and Windows? No problem.

Introductory Articles

Note that many links below refer to Hudson, the original name of Jenkins.

...

Getting started

See https://

...

jenkins.

...

io/

...

doc/

...

Test Drive

You can launch Jenkins with Java Web Start if you want to give it a test drive. Once it launches, visit http://localhost:8080/ in your browser to get to the dashboard. Any configuration that you do with this Jenkins instance will be stored in ~/.jenkins, so your data will survive a Jenkins process restart.

Installation

You have several options for downloading and installing Jenkins:

Who is using it?

A lot of companies and organizations are using Jenkins. Most instances tend to run inside the firewall, but Google can tell you publicly visible instances. We also have some statistics collected from the anonymous usage survey here. The following case studies go into more detail how Jenkins is used:

pipeline/tour/getting-started/

Installation

See https://jenkins.io/doc/book/installing/

License

Jenkins is distributed under the MIT License.