Web UI overview in Jenkins - Mini Project: Build & Apply

Jenkins Web UI Overview

📖 Scenario: You are starting to use Jenkins, a popular tool to automate software building and testing. Jenkins has a Web User Interface (UI) that helps you manage your projects easily.Imagine you want to organize your Jenkins dashboard by creating folders to keep your projects tidy.

🎯 Goal: Learn how to create a folder in Jenkins Web UI and add a simple freestyle project inside it.

📋 What You'll Learn

Access Jenkins Web UI

Create a folder named MyFolder

Create a freestyle project named MyProject inside MyFolder

Configure the project with a simple description

View the project inside the folder on the Jenkins dashboard

💡 Why This Matters

🌍 Real World

Jenkins Web UI is widely used by developers and DevOps engineers to manage automated builds and deployments in software projects.

💼 Career

Knowing how to navigate and organize Jenkins projects via the Web UI is essential for roles in software development, testing, and DevOps automation.

1

Open Jenkins Web UI and create a folder

Open Jenkins Web UI in your browser. Click on New Item. Enter the name MyFolder. Select Folder as the item type. Click OK to create the folder.

Jenkins

# Open Jenkins Web UI and create a folder named 'MyFolder'
# Your code here

Hint

Look for the New Item button on the Jenkins dashboard to start creating a folder.

2

Create a freestyle project inside the folder

Inside the MyFolder folder, click New Item. Enter the name MyProject. Select Freestyle project as the item type. Click OK to create the project.

Jenkins

# Inside 'MyFolder', create a freestyle project named 'MyProject'
# Your code here

Hint

Open the folder you created, then use New Item to add a freestyle project.

3

Add a description to the freestyle project

In the MyProject configuration page, find the Description field. Enter the text Sample project for learning Jenkins UI. Click Save at the bottom of the page.

Jenkins

# Add a description to 'MyProject' and save the configuration
# Your code here

Hint

Look for the Description box on the project configuration page to add text.

4

View the project inside the folder on the dashboard

Go back to the Jenkins dashboard. Click on the folder named MyFolder. Verify that the project MyProject is listed inside the folder.

Jenkins

# View 'MyProject' inside 'MyFolder' on the Jenkins dashboard
# Your code here

Hint

Click the folder on the dashboard to see the projects inside it.

Practice

1. What is the primary purpose of the Jenkins Web UI?

easy

A. To control and manage automation tasks like builds and configurations

B. To write code for Jenkins plugins

C. To install Jenkins on a server

D. To monitor server hardware status

Solution

1. Step 1: Understand Jenkins Web UI role

   The Jenkins Web UI acts as the main control panel for users to manage automation tasks.

2. Step 2: Compare options with UI purpose

   Only To control and manage automation tasks like builds and configurations describes managing builds and configurations, which matches the UI's purpose.

3. Final Answer:

   To control and manage automation tasks like builds and configurations -> Option A

4. Quick Check:

   Jenkins Web UI = Control panel for automation [OK]

Hint: Think: What do you do on Jenkins main screen? [OK]

Common Mistakes:

• Confusing UI with installation process
• Thinking UI is for coding plugins
• Assuming UI monitors hardware

2. Which URL format is correct to access Jenkins Web UI if the server IP is 192.168.1.10 and default port is used?

easy

A. https://192.168.1.10:80/

B. http://192.168.1.10:22/

C. ftp://192.168.1.10:8080/

D. http://192.168.1.10:8080/

Solution

1. Step 1: Identify Jenkins default port and protocol

   Jenkins uses HTTP protocol and default port 8080 for Web UI access.

2. Step 2: Match URL format with IP and port

   http://192.168.1.10:8080/ uses http with port 8080, matching Jenkins default access method.

3. Final Answer:

   http://192.168.1.10:8080/ -> Option D

4. Quick Check:

   Jenkins URL = http + 8080 port [OK]

Hint: Jenkins default port is 8080 with HTTP [OK]

Common Mistakes:

• Using HTTPS instead of HTTP by default
• Using wrong ports like 80 or 22
• Using FTP protocol mistakenly

3. After logging into Jenkins Web UI, you click on a job named BuildApp. What will you most likely see next?

medium

A. The job's build history, status, and options to start a new build

B. The Jenkins system logs and server status

C. A list of all Jenkins users and their permissions

D. The Jenkins installation wizard

Solution

1. Step 1: Understand what clicking a job shows

   Clicking a job in Jenkins UI shows details about that job, including build history and controls.

2. Step 2: Match options with expected job page content

   The job's build history, status, and options to start a new build correctly describes the job page content with build history and start options.

3. Final Answer:

   The job's build history, status, and options to start a new build -> Option A

4. Quick Check:

   Job page = build history and controls [OK]

Hint: Job page shows build info and start button [OK]

Common Mistakes:

• Confusing job page with system logs
• Expecting user list on job page
• Thinking installation wizard appears here

4. You try to access Jenkins Web UI but get a "Connection refused" error in your browser. What is the most likely cause?

medium

A. Your browser does not support HTTP protocol

B. You entered the wrong username in the login form

C. Jenkins server is not running or port 8080 is blocked

D. Jenkins Web UI requires FTP access

Solution

1. Step 1: Analyze "Connection refused" meaning

   This error means the browser cannot connect to the server at the specified address and port.

2. Step 2: Identify common causes

   Most common causes are Jenkins server not running or firewall blocking port 8080.

3. Final Answer:

   Jenkins server is not running or port 8080 is blocked -> Option C

4. Quick Check:

   Connection refused = server down or port blocked [OK]

Hint: Connection refused means server or port issue [OK]

Common Mistakes:

• Thinking it's a login username error
• Assuming browser protocol support is the problem
• Confusing HTTP with FTP requirement

5. You want to configure a new Jenkins job using the Web UI. Which sequence of actions is correct?

hard

A. Click 'New Build' > Enter job name > Configure settings > Click 'Start'

B. Click 'New Item' > Enter job name > Select job type > Click 'OK' > Configure settings > Save

C. Click 'Build Now' > Enter job name > Select job type > Save

D. Click 'Manage Jenkins' > Select 'New Job' > Enter job name > Save

Solution

1. Step 1: Identify how to create a new job in Jenkins UI

   The correct way is to click 'New Item', enter a name, select type, then configure and save.

2. Step 2: Compare options with correct job creation flow

   Only Click 'New Item' > Enter job name > Select job type > Click 'OK' > Configure settings > Save matches the official Jenkins job creation sequence.

3. Final Answer:

   Click 'New Item' > Enter job name > Select job type > Click 'OK' > Configure settings > Save -> Option B

4. Quick Check:

   New job = New Item > name > type > configure > save [OK]

Hint: New job starts with 'New Item' button [OK]

Common Mistakes:

• Using 'Manage Jenkins' for new jobs
• Clicking 'Build Now' before creating job
• Confusing 'New Build' with job creation