{{TableOfContents}}

Here is some information about the main dashboard view in Jenkins, in Fuego:

If you click on "Home" in the upper left part of any page in the fuego web
interface, you will be taked to a page with the following parts:
 * top of screen are some logos and a search bar
 * a navigation bar below that (with a context trail)
 * a sidebar of the left of the page with:
   * a menu
   * test run queue
   * target status
 * the main test history/selection panel, consisting of several tabs:
   * 0.History
   * Benchmarks
   * Functional
   * all
   * batch_runs
   * + sign

To see the configuration for each view, select the tab you want to view/edit,
and select "Edit Dashboard" in the left sidebar menu.

For each Dashboard (pane?) you can set:
 * Name, Description
 * Job Filters
   * You can select individual tests, or use a regular expression to include tests in the view
 * columns
   * you can add or remote columns, or reorder the columns
     * possible columns:
       * Compact Column: All Statuses
       * Compact Column: Stable + Failed
       * Compact Column: Test Name
       * Compact Column: Unstable + Stable
       * Last Failure
       * Last Run Duration
       * Last Stable
       * Last Success
       * Name
       * OSV Framework Column: Device
       * OSV Framework Column: Platform SDK
       * Priority Value
       * Run Test Button
       * Status
       * Test New w/ Status Color
       * Weather
 * Dashboard Portlets
 * Portlets at the top of the page
 * Portlets in the left column
 * Portlets in the right column
 * portlets at the bottom of the page

0.History dashboard [edit section]

= 0.History dashboard =
The 0.History dashboard has a regular expression to show Functional and Benchmark tests, with columns:
 * Status, Weather, Name, Run Test Button, Last Run Duration, OSV Framework Column: Device

It has a "Latests tests runs" portlet, and a "Test Run statistics" portlet at the top of the page.

Latest tests runs" portlet [edit section]

== Latest tests runs" portlet ==
The Latest tests runs" portlet has the following columns:
 * Test, Run, Time, Platform SDK, Device

where is configuration? [edit section]

=== where is configuration? ===
"Latest tests runs" is mentioned in
 * /userdata/conf/config.xml
   * value for <name>
 * /var/lib/jenkins/plugins/dashboard-view/WEB-INF/classes/hudson/plugins/view/dashboard/Messages_en_US.properties
   * value for: Dashboard.LatestBuilds
 * /fuego-install/jenkins-updates/en_US/plugins/dashboard-view/WEB-INF/classes/hudson/plugins/view/dashboard/Messages_en_US.properties
   * value for: Dashboard.LatestBuilds

Benchmarks dashboard [edit section]

= Benchmarks dashboard =
The Benchmarks dashboard has a regular expression to show Benchmark tests, with columns:
 * Status, Weather, Run Test Button, Test Name w/ Status Color, Priority Value, Last Run Duration, OSV Framework Column: Device

It has a "Tests list" portlet defined to be shown at the bottom of the page.

Available portlets [edit section]

== Available portlets ==
Available Dashboard portlets are:
 * Latest tests runs
 * Test Run statistics
 * Test Statistics Chart
 * Test Statistics Grid
 * Test Trend Chart
 * Test statistics
 * Tests Grid
 * Tests list
 * Unstable Tests

Notes [edit section]

= Notes =
Comment: tbwiki formatting is a dream compared to this Jenkins/Hudson/java/js/groovy/stapler/jelly mess!

the 0.History notepad icon mystery [edit section]

== the 0.History notepad icon mystery ==
Where does the notepad icon come from, in the 0.History list, and what does it mean?

Note: The code for this appears to have been coded by Kohsuke Kawaguchi himself (sometime between 2004 and 2009)

this dashboard portlet is labeled "Latest tests runs", and is a "LatestBuild" portlet in the plugin source.

The "LatestBuild" jelly (xml used for HTML emission??) is located at:
 * /var/lib/jenkins/plugins/dashboard-view/WEB-INF/classes/hudson/plugins/view/dashboard/builds/LatestBuilds/latestbuilds.jelly
   * this file has the definitions for the table to show each row of information
      * the Test is defined with <dp:jobLink job="${build.parent} note="${build.description}"/>

• dp: must be some kind of jelly directive * note: there's a t: jelly directive in a comment in the file.

        * dp: must be some kind of jelly directive
          * note: there's a t: jelly directive in a comment in the file.

• the jobLink.jelly file has more info: * there's a test in: * /var/lib/jenkins/plugins/dashboard-view/WEB-INF/classes/hudson/view/dashboard/jobLink.jelly * here's the test: * <j: if test="${!empty(build.description)}"> * then emit a notepag.png with a tooltip ${note} with href ${job.shortUrl} * test is follow by jelly code to emit test name with tooltip of description

 * the jobLink.jelly file has more info:
   * there's a test in:
      * /var/lib/jenkins/plugins/dashboard-view/WEB-INF/classes/hudson/view/dashboard/jobLink.jelly
     * here's the test:
       * <j: if test="${!empty(build.description)}">
         * then emit a notepag.png with a tooltip ${note} with href ${job.shortUrl}
     * test is follow by jelly code to emit test name with tooltip of description

So the answer appears to be that this test in jobLink.jelly for a
non-empty build.description controls whether the entry includes a little
notepad.png icon (with a link to the job (shortUrl).