Rewrite the build history widget

[janfaracik]

This PR implements the changes discussed https://community.jenkins.io/t/revamped-build-history-widget/10944. In essence it's a rewrite/redesign of the build history widget. The goal is to be cleaner and simpler, whilst still retaining existing functionality and density.

Before

After

What's changed

• The JS has been rewritten and does away with a lot of the complicated layout logic in favour of CSS flex/grid.
• A new card component has been added (with the intention of replacing the existing widget component) that supports inline actions
• Builds now group by date, keeping the UI simpler/easier to read
• RSS feed has been moved to a dropdown, rather than a fixed button row
• Build overflow menus are now always present on the right of the link

What doesn't work

• ✅ Pagination controls are always visible at the moment
• ✅ The list doesn't auto refresh at the moment
• ✅ Items with long names/lots of actions don't scale very well

Testing done

• See Rewrite the build history widget #9148 (comment) for a view of the scenarios tested
  • Normal scenarios work as expected (e.g. short build names, one or two badges)
  • Queued items look as expected
  • Items with plain text/HTML descriptions work as expected
  • Items with long names/lots of badges wrap as expected

Proposed changelog entries

• Update the design of the build history widget

Proposed upgrade guidelines

N/A

Submitter checklist

Edit tasklist title

Beta Give feedback Tasklist Submitter checklist, more options

• Rename
• Copy markdown
• Delete tasklist

Delete tasklist

Delete tasklist block?

Are you sure? All relationships in this tasklist will be removed.

Cancel Delete

1. The Jira issue, if it exists, is well-described.

   The Jira issue, if it exists, is well-described.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
2. The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see [examples](https://github.com/jenkins-infra/jenkins.io/blob/master/content/_data/changelogs/weekly.yml)). Fill in the **Proposed upgrade guidelines** section only if there are breaking changes or changes that may require extra steps from users during upgrade.

   The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
3. There is automated testing or an explanation as to why this change has no tests.

   There is automated testing or an explanation as to why this change has no tests.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
4. New public classes, fields, and methods are annotated with `@Restricted` or have `@since TODO` Javadocs, as appropriate.

   New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
5. New deprecations are annotated with `@Deprecated(since = "TODO")` or `@Deprecated(forRemoval = true, since = "TODO")`, if applicable.

   New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
6. New or substantially changed JavaScript is not defined inline and does not call `eval` to ease future introduction of Content Security Policy (CSP) directives (see [documentation](https://www.jenkins.io/doc/developer/security/csp/)).

   New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.

   For dependency updates, there are links to external changelogs and, if possible, full differentials.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
8. For new APIs and extension points, there is a link to at least one consumer.

   For new APIs and extension points, there is a link to at least one consumer.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove

Add item to Submitter checklist

Desired reviewers

@jenkinsci/sig-ux

Before the changes are marked as ready-for-merge:

Maintainer checklist

Edit tasklist title

Beta Give feedback Tasklist Maintainer checklist, more options

• Rename
• Copy markdown
• Delete tasklist

Delete tasklist

Delete tasklist block?

Are you sure? All relationships in this tasklist will be removed.

Cancel Delete

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.

   There are at least two (2) approvals for the pull request and no outstanding requests for change.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.

   Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
3. Changelog entries in the pull request title and/or **Proposed changelog entries** are accurate, human-readable, and in the imperative mood.

   Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
4. Proper changelog labels are set so that the changelog can be generated automatically.

   Proper changelog labels are set so that the changelog can be generated automatically.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
5. If the change needs additional upgrade steps from users, the `upgrade-guide-needed` label is set and there is a **Proposed upgrade guidelines** section in the pull request title (see [example](https://github.com/jenkinsci/jenkins/pull/4387)).

   If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a _Bug_ or _Improvement_, and be labeled as `lts-candidate` to be considered (see [query](https://issues.jenkins.io/issues/?filter=12146)).

   If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove

Add item to Maintainer checklist

[timja]

can you add before screenshots too please

[mawinter69]

How does this look when a build has a display name?
How does it look when a build has many badges?
Just an example how this looks currently:

[janfaracik]

How does this look when a build has a display name? How does it look when a build has many badges? Just an example how this looks currently:

It's okay but could be better - I think moving the badges onto a new row when its incredibly long would improve it.

[mawinter69]

What made the previous implementation so big was the logic to find a suitable way to arrange all the things. See #9122 for my PR that changed they calculation to be more efficient.

[github-actions]

Please take a moment and address the merge conflicts of your pull request. Thanks!

[janfaracik]

Getting ReferenceError: "fetch" is not defined. (http://localhost:42617/jenkins/static/8bd93229/jsbundles/pages/project/builds-card.js#52) in tests - have you experienced this before @timja?

[timja]

Getting ReferenceError: "fetch" is not defined. (http://localhost:42617/jenkins/static/8bd93229/jsbundles/pages/project/builds-card.js#52) in tests - have you experienced this before @timja?

I see the issue, PR incoming

[timja]

jenkinsci/jenkins-test-harness#753

[mawinter69]

Looks good now

Some minor thought:

• the navigation buttons are at the bottom. so when I want to look at later builds I need to scroll down first

Here a screenshot with some badges:

[mawinter69]

This makes the status icon 20x20, before it was 16x16. Is this intentional?
The badges stay with 16x16

[janfaracik]

I think so, think the status icon is the most important icon overall so doesn't hurt to be a touch larger.

[strangelookingnerd]

FWIW the icons in badges of course can be bigger but really shouldn’t because they won’t align with the text height anymore. The latter is also the case with the build status icon being 20x20. I just found it odd that they became bigger (jenkinsci/badge-plugin#151 (comment))

[timja]

Badges can overflow the box:

May not be realistic but is it fixable without too much effort?

the navigation buttons are at the bottom. so when I want to look at later builds I need to scroll down first

Its normal for pagination to be at the bottom, I think this should be fine

[mawinter69]

I'm not able to reproduce the badge overflowing, but having many badges with icons from Badge plugin leads to the icons getting very small. Probably also an issue with the badge plugin itself. But ideally the badges would start flowing in the next row.

Seems with the refactoring of the badge plugin things do indeed overflow.

[timja]

I just copied the examples for symbols from the pipeline syntax page and repeated twice in addBadge

addBadge icon: 'symbol-alert-circle-outline plugin-ionicons-api', text: 'This is an alert symbol'
addBadge icon: 'symbol-bar-chart-filled plugin-ionicons-api', text: 'This is a bar chart symbol'
addBadge icon: 'symbol-battery-half-sharp plugin-ionicons-api', text: 'This is a half filled battery symbol'
addBadge icon: 'symbol-flag-outline plugin-ionicons-api', text: 'This is a flag symbol'
addBadge icon: 'symbol-mic plugin-ionicons-api', text: 'This is a microphone symbol'
addBadge icon: 'symbol-rocket-filled plugin-ionicons-api', text: 'This is a rocket'
addBadge icon: 'symbol-unlink-sharp plugin-ionicons-api', text: 'This is an unlink symbol'

addBadge icon: 'symbol-alert-circle-outline plugin-ionicons-api', text: 'This is an alert symbol'
addBadge icon: 'symbol-bar-chart-filled plugin-ionicons-api', text: 'This is a bar chart symbol'
addBadge icon: 'symbol-battery-half-sharp plugin-ionicons-api', text: 'This is a half filled battery symbol'
addBadge icon: 'symbol-flag-outline plugin-ionicons-api', text: 'This is a flag symbol'
addBadge icon: 'symbol-mic plugin-ionicons-api', text: 'This is a microphone symbol'
addBadge icon: 'symbol-rocket-filled plugin-ionicons-api', text: 'This is a rocket'
addBadge icon: 'symbol-unlink-sharp plugin-ionicons-api', text: 'This is an unlink symbol'

addBadge icon: 'symbol-alert-circle-outline plugin-ionicons-api', text: 'This is an alert symbol'
addBadge icon: 'symbol-bar-chart-filled plugin-ionicons-api', text: 'This is a bar chart symbol'
addBadge icon: 'symbol-battery-half-sharp plugin-ionicons-api', text: 'This is a half filled battery symbol'
addBadge icon: 'symbol-flag-outline plugin-ionicons-api', text: 'This is a flag symbol'
addBadge icon: 'symbol-mic plugin-ionicons-api', text: 'This is a microphone symbol'
addBadge icon: 'symbol-rocket-filled plugin-ionicons-api', text: 'This is a rocket'
addBadge icon: 'symbol-unlink-sharp plugin-ionicons-api', text: 'This is an unlink symbol'

[mawinter69]

I added addShortText(text: "A somewhat longer badge that might overflow") maybe that leads to a different behaviour.

[janfaracik]

Badges now wrap - good spot