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'.