Skip to content
Tutorials Center
My learning

Topics

Lesson 5 of 40 ยท Meet Jenkins

A Tour of the Jenkins Interface

Find your way around Jenkins: the dashboard, views, job pages, build history, console output, Manage Jenkins, Blue Ocean versus the modern UI, and quick search.

Jenkins has a plain, practical web interface. It will not win design awards, but once you know where things are, you can answer the questions that matter in seconds: What is broken? Who broke it? What did the log say? Is anything waiting? This lesson is a guided tour of the main screens and the small symbols you will see all the time.

The interface itself cannot be reproduced on this page, so the tour describes each screen in words and read-only URL patterns. A stand-in at the end re-implements two of Jenkins' small rules, the build status colours and the "weather" icon, so you can see how they are computed. Screens differ slightly between Jenkins versions and themes, so treat the names as signposts rather than pixel-perfect descriptions.

Where to look first

Dashboard All jobs, with status and weather.
Job page Build history and the stage view.
Console output The full log of one build.
Manage Jenkins Settings, plugins, nodes, security.

Dashboard, then job, then build, then console. Zoom in one level at a time.

1 / 2

The dashboard and views

After login you land on the dashboard, a table with one row per job. Each row shows:

  • a status ball for the last build,
  • a weather icon for the recent trend,
  • the job name, the time since last success, last failure and last duration.

When you have many jobs, scrolling gets tiring, so Jenkins offers views: tabs at the top of the dashboard that filter jobs. A view can list jobs you pick by hand, jobs whose names match a regular expression (such as ^payments-.*), or a mix. Views are only a filter; deleting a view never deletes jobs. For larger organisations, folders group jobs into a real hierarchy with their own permissions and credentials.

On the left of the dashboard you will also find New Item (create a job), Build History (a timeline of recent builds across all jobs) and Build Queue and Build Executor Status, two small panels that show what waits and what runs. They are the first place to look when "nothing is happening".

The job page

Click a job and you see its job page. Typical parts:

  • Build Now (or Build with Parameters if the job takes inputs).
  • Configure, where you edit the job definition. For a pipeline job, the definition may live in a Jenkinsfile instead.
  • A Build History list with numbers like #42, each with its status ball and time. Click a number to open that build.
  • For pipelines, a stage view or a graph showing each stage as a box coloured by result, which makes it obvious which stage failed.
  • Workspace, a browser for the files left on the agent by the last build.
  • Links such as Changes (commits since the last build) and Test Result (if you publish test reports).

The URL structure is regular, and it is useful to know:

TEXT
/job/my-app/                 the job page
/job/my-app/42/              build #42
/job/my-app/42/console       the log, styled
/job/my-app/42/consoleText   the log as plain text
/job/my-app/lastBuild/       the latest build
/job/my-app/lastSuccessfulBuild/
/job/my-folder/job/my-app/   a job inside a folder

The build page and console output

The build page for #42 shows the status, the trigger ("Started by user ana", "Started by an SCM change"), the commits it contained, and the artifacts it saved. The most-visited link is Console Output, the log of everything the build did, in order.

Reading a console log is a skill. Tips:

  • Start at the bottom: the last lines say whether the build finished with Finished: SUCCESS, FAILURE or UNSTABLE.
  • Then scroll upwards to the first error, not the last. Later errors are often side effects.
  • In pipeline logs, each stage and step prints a header, so you can find the stage fast.
  • For long logs use the plain text link and Ctrl+F, or download it.

Here is a shortened, read-only example of a console log:

TEXT
Started by user ana
Running as SYSTEM
Building in workspace /var/lib/jenkins/workspace/my-app
[my-app] $ /bin/sh -xe /tmp/jenkins1234.sh
+ echo Hello from Jenkins
Hello from Jenkins
+ ./run-tests.sh
FAIL: checkout total should be 42
Build step 'Execute shell' marked build as failure
Finished: FAILURE

Manage Jenkins

Click Manage Jenkins on the left for the control room. Its sections change a little between versions, but you will find these groups:

  • System (global settings: Jenkins URL, email, global environment variables, number of executors).
  • Tools (JDK, Maven, Git and other tool installations).
  • Plugins (installed, updates, available, advanced).
  • Nodes (agents and the controller's executors).
  • Security and Credentials (who can do what, and the secret store).
  • System Log and System Information (diagnostics).
  • Script Console (a Groovy shell inside the server; powerful and dangerous, see Security, Users and Authorization).

Near the top, Jenkins lists warnings and monitors: an outdated plugin, an insecure setting, a reverse-proxy problem, low disk space. Read them whenever you open the page; they are Jenkins telling you what it worries about.

Blue Ocean versus the modern interface

You may read about Blue Ocean, a plugin that gave Jenkins a pretty, pipeline-focused interface years ago. It is no longer receiving feature development, and the project's direction is to improve the standard interface instead, with pipeline visualisation available through plugins such as the stage view or the pipeline graph view. If you see Blue Ocean in an old guide, you can follow the concepts but expect the screens in current Jenkins to look different. Learn the standard UI; it is where the project is going.

Searching and keyboard use

The search box at the top of the page finds jobs, builds, nodes and settings by name. Recent Jenkins versions also provide a command palette, opened with a keyboard shortcut (commonly Ctrl+K), that jumps straight to pages and actions. Browser features help too: bookmark the URLs of your most important jobs, and keep the console output open in a tab while a build runs, because it streams live.

A stand-in for status colours and weather

Jenkins computes the weather icon from the last five builds of a job: the more of them that were stable, the sunnier the icon. The stand-in below applies this idea. It is a model of the rule, not Jenkins' own code, and the exact thresholds are described in simplified form: 80 % or more is sunny, 60 to 79 partly cloudy, 40 to 59 cloudy, 20 to 39 rainy, below 20 stormy.

JS A stand-in for status balls and weather

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The web-app job is sunny and blue. api has a blue ball now but only 60 % stable builds recently, so the weather is partly cloudy: the ball shows the latest build, the weather shows the trend. legacy is red and rainy. Teams often put the dashboard on a wall screen, and this pair of symbols is why it works.

A second stand-in shows how to pick out the most urgent job from the same data, the way you would scan the dashboard by eye.

JS Which job needs attention first?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

When you are new to a Jenkins server, spend five minutes on the dashboard, the build queue and Manage Jenkins before touching anything. You will learn what the team builds, how healthy it is and what the server is worried about.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does the weather icon on the dashboard represent?

    The ball shows the latest build; the weather summarises the last five. A job can be blue with cloudy weather if it recovered recently.
  2. 2. A yellow ball usually means:

    Yellow means UNSTABLE: the build ran, but something such as test results marked it as not fully healthy.
  3. 3. You open a failed build's console output. Where is a good place to start reading?

    The last lines give the verdict, and the first error is usually the cause. Later errors are often consequences.
  4. 4. What is the status of Blue Ocean today?

    Blue Ocean is in maintenance. Learn the standard interface, which is where improvements now go.

Summary

  • The dashboard lists jobs with a status ball (latest build) and weather icon (recent trend); views filter it and folders group jobs.
  • A job page leads to build pages (#N), whose Console Output is the log you will read most.
  • Manage Jenkins holds system settings, tools, plugins, nodes, security, credentials and diagnostics, plus warnings worth reading.
  • Blue Ocean is legacy; learn the standard UI.
  • Use search, bookmarks and predictable URLs (/job/NAME/lastBuild/console) to move fast.

Now create something to look at, in Your First Job: Freestyle Projects.