Install Jenkins on Windows: Step-by-Step Guide

Yes, you can install Jenkins on Windows, and the most straightforward method is to use the official Windows installer, which runs Jenkins as a Windows service. This guide walks you through the entire process—from checking Java prerequisites to accessing your Jenkins dashboard—and covers common setup pitfalls so you can get a working CI/CD server quickly.

What Is Jenkins and Why Use It on Windows?

Jenkins is an open-source automation server used for continuous integration (CI) and continuous delivery (CD). It automates building, testing, and deploying software. While Jenkins runs natively on Linux and macOS, Windows is a common environment for many development teams, especially those building .NET applications or working in mixed-platform shops. Installing Jenkins on Windows gives you the same pipeline automation capabilities without needing a separate Linux VM or container.

The Windows installer handles the heavy lifting: it installs Jenkins as a service, sets up the local file structure, and configures the service to start automatically. This means Jenkins runs in the background even when no user is logged in, which is ideal for a build server. You can also run Jenkins as a standalone Java process (via the WAR file) if you prefer more control, but the service approach is simpler for most users.

Prerequisites: Java and System Requirements

Jenkins is a Java application, so you need a Java Runtime Environment (JRE) installed before you start. As of Jenkins 2.357 and later, Jenkins requires Java 11 or Java 17 (Java 8 is no longer supported). For the latest versions, Java 17 is recommended. You can check your installed Java version by opening a command prompt and typing:

java -version

If Java is not installed, download the OpenJDK or Oracle JDK installer from a trusted source and install it. Make sure the java command is in your PATH, or the Jenkins installer will fail to find it.

Other requirements are modest: a 64-bit Windows version (Windows 10, Windows 11, or Windows Server 2016+), at least 2 GB of RAM (4 GB recommended), and about 10 GB of free disk space for Jenkins itself plus your build artifacts. More disk space will be needed if you plan to store many build logs or artifacts.

Step-by-Step: Installing Jenkins Using the Windows Installer

Download the Jenkins installer from the official Jenkins website (jenkins.io). Look for the “Windows” option under the “Download” section. The file is typically named jenkins.msi.
Run the installer as Administrator. Right-click the MSI file and select “Run as administrator” to avoid permission issues.
Follow the setup wizard. You will be asked to choose the installation directory (default is C:\Program Files\Jenkins) and the service logon account. The default is “Local System”, which works for most setups. If you need Jenkins to access network resources, you may want to specify a domain user later.
Set the port number. The default is 8080. If that port is already in use, choose another (e.g., 8081). You can also change the port later by editing the Jenkins configuration file.
Select the Java path. The installer should detect your Java installation automatically. If not, browse to the java.exe file.
Finish the installation. The installer will start Jenkins as a Windows service. You can verify it is running by opening the Services app (services.msc) and looking for “Jenkins”.
Access Jenkins. Open a browser and go to http://localhost:8080 (or the port you chose). You will see the “Unlock Jenkins” page with an initial admin password.

Initial Setup: Unlocking Jenkins and Creating an Admin User

When you first access Jenkins, it asks for an initial admin password. This password is generated during installation and is stored in a file on your system. To find it, open the file C:\Program Files\Jenkins\secrets\initialAdminPassword in a text editor. Copy the password and paste it into the Jenkins setup page.

After unlocking, you can choose to install suggested plugins or select specific plugins yourself. For a first-time setup, the “Install suggested plugins” option is the easiest—it includes the most common plugins for Git, Maven, and build tools. The installation may take a few minutes.

Finally, create the first admin user. Enter a username, password, and email address. This user will have full administrative rights. After that, Jenkins is ready to use.

Common Problems and How to Fix Them

Despite the installer’s simplicity, a few issues are common:

Java not found: If the installer complains about Java, ensure Java is installed and that JAVA_HOME environment variable is set. You can set it manually: go to System Properties > Environment Variables and add JAVA_HOME pointing to your JDK installation folder.
Port 8080 already in use: If another application (like a web server) is using port 8080, Jenkins will fail to start. Change the port during installation, or later by editing the jenkins.xml file in the Jenkins installation directory and restarting the service.
Service won’t start: Check the Windows Event Viewer for errors. Often this is due to incorrect file permissions or a missing Java path. Re-run the installer and ensure the Java path is correct.
Initial password file not found: If you can’t find the initialAdminPassword file, check the Jenkins log file (usually in C:\Program Files\Jenkins\jenkins.err.log) for the generated password, or try restarting the Jenkins service to regenerate it.

Running Jenkins as a Standalone Process (Alternative Method)

If you prefer not to use the service installer, you can download the Jenkins WAR file and run it with Java. This method gives you more control but requires manual setup for auto-start and running as a background process. Steps:

Download the jenkins.war file from the official site.
Open a command prompt and navigate to the folder containing the WAR file.
Run the command: java -jar jenkins.war --httpPort=8080. This starts Jenkins in the foreground.
Access Jenkins at http://localhost:8080 and follow the same initial setup.

To stop Jenkins, press Ctrl+C in the command prompt. This method is handy for testing or when you don’t have administrator rights to install a service.

Configuration After Installation: What to Do Next

Once Jenkins is running, you may want to adjust a few settings:

Change the port: Edit the jenkins.xml file (or the --httpPort argument) and restart the service.
Set up build agents: For larger projects, you can connect additional Windows or Linux machines as agents to distribute workloads.
Configure global security: By default, Jenkins uses its own user database. You can integrate with Active Directory or other SSO providers if needed.
Install plugins: Use the “Manage Jenkins” > “Plugins” section to install plugins for your specific tools (e.g., MSBuild, Docker, Kubernetes).
Backup configuration: Regularly back up the C:\Program Files\Jenkins folder (or your JENKINS_HOME) to avoid losing job configurations.

Frequently Asked Questions

Can I install Jenkins on Windows without Java?

No, Jenkins requires Java to run. The installer will not proceed without a valid JRE. You must install Java 11 or 17 (depending on the Jenkins version) before running the installer.

How do I change the Jenkins port after installation?

Open the file jenkins.xml in the Jenkins installation directory (usually C:\Program Files\Jenkins). Find the --httpPort=8080 argument and change the number. Save the file and restart the Jenkins service from the Services app.

Why is Jenkins not starting after installation?

Common causes include port conflicts, incorrect Java path, or insufficient permissions. Check the Windows Event Viewer for error logs. Verify that port 8080 is free, Java is installed correctly, and the Jenkins service account has access to the installation folder.

Can I run Jenkins on Windows 11?

Yes, Jenkins runs on Windows 11 as long as you have Java 11 or 17 installed. The installer works the same as on Windows 10.

What is the default Jenkins admin password?

There is no default password. The initial password is randomly generated and stored in C:\Program Files\Jenkins\secrets\initialAdminPassword. You use this password only once to unlock the setup wizard, after which you create your own admin user.

Is it better to run Jenkins in Docker on Windows?

It depends on your needs. Running Jenkins in Docker is portable and easier to upgrade, but requires Docker Desktop and may have file permission complexities on Windows. The native installer is simpler for a dedicated build server and integrates better with Windows services.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →