Skip to content
Get packs

Guide · Open source

How to use Jenkins: install, set up and automate builds

Updated · written with AI from the project's own documentation and checked against our catalogue data

Jenkins is an open-source automation server written in Java. It runs repetitive software tasks such as building projects, running tests, static code analysis and deployment, so teams can find problems soon after code changes. This guide explains what Jenkins is for, how to get a copy, what you need before installing it, and where to look next.

Jenkinsjenkinsci/jenkins · ★ 26.7k · MIT

Quick start

  1. 1Check prerequisites. Make sure Java is installed on the machine that will run Jenkins. Confirm the required version in the official documentation, since the README does not state one.
  2. 2Choose a release line. Pick Weekly for the newest features or LTS for the periodically backported bug-fix line.
  3. 3Download a distribution. Get the WAR file, Docker image, native package or installer for your platform from the Jenkins downloads page.
  4. 4Run Jenkins. Start the Jenkins server on the machine you prepared, following the installation steps for your chosen distribution.
  5. 5Create a build or test job. Set up a job that builds your project or runs your tests so Jenkins can run it automatically.
  6. 6Add plugins as needed. Search the Plugins Index and install only the plugins your workflow requires.

What is Jenkins used for?

Jenkins automates parts of a software development workflow. The project lists the most common uses as building projects, running tests to detect bugs as soon as they are introduced, static code analysis, and deployment.

  • Building projects
  • Running tests to detect bugs and other issues as soon as they are introduced
  • Static code analysis
  • Deployment

What do you need before installing Jenkins?

Jenkins is written in Java, so Java must be available on the machine that runs it. The README does not specify which Java version is required, so check the official Jenkins documentation before you install.

Jenkins is a server you run yourself. The project describes it as something you install, so it is not a hosted service that needs no server.

  • Java installed on the host machine (the source does not specify a version)
  • A machine you can run a server on
  • A software delivery workflow to automate

How do you download Jenkins?

The Jenkins project provides official distributions as WAR files, Docker images, native packages and installers for platforms including several Linux distributions and Windows. The downloads page at jenkins.io lists the references for each.

Jenkins offers two release lines. Weekly releases include all new features, improvements and bug fixes. Long-Term Support (LTS) is an older release line that receives periodic bug fix backports, and is the more conservative choice for most teams.

  • Weekly: frequent releases with all new features, improvements and bug fixes
  • Long-Term Support (LTS): older line updated periodically via bug fix backports

How do you get the Jenkins source code?

If you want to work from the source rather than a packaged distribution, the project's source is hosted on GitHub. Clone the repository with the command below. The source repository is the place to look for contribution guidelines and developer documentation.

git clone https://github.com/jenkinsci/jenkins

How do you extend Jenkins with plugins?

Jenkins is built to be extended. The README says it provides over 2,000 plugins to support automating many kinds of tasks. The Plugins Index lists what is available, and the documentation explains how to add them.

Because the plugin catalogue is large, choose only the plugins your workflow needs. Each extra plugin is something you must keep working alongside the rest of your setup.

  • Browse the Plugins Index at plugins.jenkins.io
  • Add only the plugins your builds, tests or deployments require

Where can you learn more and get help?

The official website at jenkins.io holds the documentation, blog posts, plugin listings and community updates. The project also runs a Gitter chat for questions and help, and a Developer Documentation section for working with Jenkins internals.

  • Documentation: jenkins.io/doc
  • Blog: jenkins.io/blog
  • Events: jenkins.io/events
  • Gitter chat for questions and help

What people use it for

  • Build a project automatically whenever its code changes
  • Run tests so bugs are reported soon after they are introduced
  • Run static code analysis as part of the development workflow
  • Automate deployment as part of a software delivery pipeline

Frequently asked questions

Is Jenkins free?

Jenkins is licensed under the MIT License, which is a permissive open-source licence. The source describes it as a free, self-hosted automation server that you install yourself.

What language is Jenkins written in?

Jenkins is written in Java. The Java version it needs is not specified in the README, so check the official documentation before installing.

Is Jenkins a hosted service?

No. The README describes installing Jenkins yourself, so you need a server to run it on. If you want a hosted service with no server to run, Jenkins is not the right fit.

How many plugins does Jenkins have?

The README says Jenkins offers over 2,000 plugins to extend what it can automate. The Plugins Index at plugins.jenkins.io lists them.

What are the alternatives to Jenkins?

Projects that are often compared with Jenkins include GitLab CI, Buildbot, Drone and GoCD. Compare them against your workflow, hosting preferences and the plugins or integrations you need.

Which Jenkins release should I use?

The source describes Weekly releases as frequent, with all new features, improvements and bug fixes. LTS is an older line that gets periodic bug fix backports, so it suits teams that prefer stability.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Jenkins suits development teams that want to automate builds, tests and deployment on a server they run themselves, with a large plugin ecosystem and an MIT licence. It is a poor fit for people who want a hosted service with no server to manage, or for non-technical users without a delivery workflow to automate.

Install options & downloads