Web UI overview in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to open the Jenkins dashboard URL.

Jenkins

Open your browser and go to http://localhost:[1]/

Drag options to blanks, or click blank then click option'

A80

B22

C443

D8080

Attempts:

3 left

💡 Hint

Common Mistakes

Using port 80 which is default for HTTP but not Jenkins.

Using port 443 which is for HTTPS.

Using port 22 which is for SSH.

The default port for Jenkins web UI is 8080. So the URL is http://localhost:8080/.

2fill in blank

medium

Complete the code to log in to Jenkins web UI with the default username.

Jenkins

Enter username: [1]

Drag options to blanks, or click blank then click option'

Aroot

Badmin

Cuser

Dguest

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'root' which is a Linux system user, not Jenkins default.

Using 'guest' which is not a Jenkins default user.

The default username for Jenkins login is 'admin'.

3fill in blank

hard

Fix the error in the Jenkins web UI URL to access the build history page.

Jenkins

http://localhost:8080/[1]/builds

Drag options to blanks, or click blank then click option'

Ajob

Bbuild

Cjobs

Dhistory

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'job' which is singular and incorrect in URL.

Using 'build' or 'history' which are not valid URL segments.

The correct path segment to access build history for jobs is 'jobs'.

4fill in blank

hard

Fill both blanks to create a Jenkins pipeline script block that echoes a message.

Jenkins

pipeline {
  agent any
  stages {
    stage('Example') {
      steps {
        [1] '[2]'
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Aecho

Bprint

CHello, Jenkins!

DHello World

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'print' which is not a Jenkins pipeline step.

Using messages without quotes.

In Jenkins pipeline scripts, the 'echo' step prints messages. 'Hello World' is a common example message.

5fill in blank

hard

Fill all three blanks to define a Jenkins freestyle job configuration snippet with a description and a build trigger.

Jenkins

<project>
  <description>[1]</description>
  <triggers>
    <hudson.triggers.SCMTrigger>[2]</hudson.triggers.SCMTrigger>
  </triggers>
  <builders>
    <hudson.tasks.Shell>[3]</hudson.tasks.Shell>
  </builders>
</project>

Drag options to blanks, or click blank then click option'

AMy first Jenkins job

B<spec>H/5 * * * *</spec>

Cecho Build started

DBuild triggered

Attempts:

3 left

💡 Hint

Common Mistakes

Putting XML tags inside description.

Missing <spec> tags for SCM trigger.

Using invalid shell commands.

The description is a simple text. The SCM trigger uses a cron spec inside <spec> tags. The shell builder runs a shell command like 'echo Build started'.

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