[JENKINS-72944] reduce spacing in buildhistory widget

[mawinter69]

the logic when name, details and badges arrangement is changed so that the available space is better used.
The stop action is no longer treated as separate thing, instead it is just like all other badges. The stop button will always be in the far right. The width calculation now considers the actual width of the content and not of the element they are in. When name and badges fit in one row they will be joined.
badges are using a flex layout that should allow for better alignement and will automatically wrap the elements though this only happen now when the badges are in their own row and still to large

Add a resize handler so when the sidepanel switch to/from tablet mode or size is changed in tablet mode then the table layout is recalculated.

The pictures show builds with many badges (gerrit, build trigger badge, keep build forever, job config change, disk usage)

Screenshots before

Full width window:

• line break inside the disk usage badge
• no space between badges
• bad alignement (see build 11530)

~850px width window

min-width window (483px)

Running build

after going to full-screen from min-width window

Screenshots after

Full width window with running build

~850px width window

min-width window (483px)

See JENKINS-72944.

Testing done

Manual testing

Proposed changelog entries

• JENKINS-72944, reduce spacing in buildhistory widget

Proposed upgrade guidelines

N/A

Submitter checklist

Beta Give feedback

1. The Jira issue, if it exists, is well-described.
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). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
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).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@mention

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

Maintainer checklist

Beta Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
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).
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).

[timja]

I haven't closed inspected the JavaScript, its quite complex. Something like handlebars would likely clean the code up a lot but may be complicated by the fact the badges are loaded in via jelly

---

Screenshots and testing looks good to me

[Kevin-CB]

I tested your PR locally, it looks fine security wise.

However, I've noticed minor bugs.
When I build an empty freestyle project and add a build description, the ordering gets messed up, placing the description first and the left bar in the middle of the character. Note that this seems to only happen on the last build.

Also, when there are no badges on my build, I encounter some errors.

[mawinter69]

However, I've noticed minor bugs. When I build an empty freestyle project and add a build description, the ordering gets messed up, placing the description first and the left bar in the middle of the character. Note that this seems to only happen on the last build.

Fixed

Also, when there are no badges on my build, I encounter some errors.

fixed

[mawinter69]

given ongoing work by @janfaracik in #9148 to rewrite the build history widget does it make sense to merge this?

[timja]

Let's mark as on-hold, we can always pick it back up later if needed.

/label on-hold

[github-actions]

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

[mawinter69]

close in favor of #9148