Jenkins – How to install Jenkins on Windows?

By | April 24, 2023

Jenkins is an open-source automation server written in the Java programming language that is used for continuous integration of software projects. It also allows continuous deployment (CI/CD) for software projects by integrating with various testing and deployment tools and technologies. To learn more about Jenkins, please refer to Jenkins: An Introduction to CI/CD and Jenkins.

Steps to install Jenkins on Windows

Step 1- Download Jenkins

First, we need to download the Jenkins. For this, go to Jenkins Official Page and click on Download.

Fig 1- Download Jenkins

The Jenkins project produces two different release version:

  1. Long-Term Support Release
    • The long-term support releases are bug-free and stable. It comes every 12 weeks and is intended for end users.
  2. Weekly Release
    • These are regular releases that come every week with bug fixes from earlier releases and are intended for plugin developers.

We will be downloading the long-term support release version of Jenkins for the Windows platform. For this, click on Download Jenkins LTS for Windows.

Jenkins LTS
Fig 2- Jenkins for Windows Platform

Step 2- Installing Jenkins

Once we have downloaded the Jenkins setup, We need to run the setup and accept the terms and license. After we run the setup, it will open a Setup Wizard, and we need to click on Next.

Fig 3- Jenkins Setup Wizard

After we click on Next, it asks for the location where we want our Jenkins server to be installed. (Here, we are using the default location.)

Fig 4- Destination Folder for Installing Jenkins

Again, we click Next, and a popup will appear asking for the logon credentials. Either we can choose Run service as LocalSystem or Run service as local or domain user, where we need to give our system’s username and password. (Here, we are choosing to run the service as LocalSystem)

Fig 5- Service Logon Credentials

Now, it will ask for the port number on which we want our Jenkins server to run. We can enter our desired port number and click on Test Port. (Here, we are choosing the default port i.e., 8080)

Jenkins Port Number
Fig 6- Jenkins Port Selection

We have configured the port number. Next, it will ask the path for JDK or JRE. Make sure that you have Java 11 or higher.

Fig 7- Java Home for Jenkins

After this, click on Next, and a Custom Setup popup will come up with the default configuration. Click on Next.

Fig 8- Custom Setup

Finally, we have accepted the terms and conditions for Jenkins installation. By clicking Next, we will get a popup to install Jenkins.

Fig 9- Install Jenkins

Once Jenkins installation is complete, click Finish to exit the setup wizard.

Fig 10- Jenkins Installation Completes

Step 3- Configure Jenkins

In this step, we need to configure Jenkins and create the first admin user to use Jenkins. After the Jenkins installation completes, as we have configured the port number 8080, we will access the Jenkins server at http://localhost:8080. It will ask to unlock Jenkins using the initial admin password, which will be present on the path it shows.

Fig 11- Unlock Jenkins

After we click Continue, we have the option to choose standard or custom plugins. (Here, we are choosing the standard plugins)

Fig 12- Install Suggested Plugins

As soon as we click on “Install suggested plugins”, Jenkins will start installing the standard required plugins.

Jenkins Plugins
Fig 13- Jenkins Standard Plugins

Jenkins asks to create the first admin user as it completes the plugin installation, where we will give the following user details and click on Save and Continue.

Setup Jenkins First Admin User
Fig 14- Jenkins First Admin User Setup

After we click Save and Continue as the admin user, it will ask for the Jenkins instance configuration. We keep it default and click Save and Finish.

Fig 15- Instance Configuration

Next, our Jenkins configuration setup is complete. Now, we just need to click on Start using Jenkins.

Fig 16- Start Jenkins

As soon as we click on Start using Jenkins, our Jenkins server starts, and we can use it for CI/CD.

Jenkins Dashboard
Fig 17- Jenkins Dashboard