[JENKINS-72711] Restore progress animation in build history and buildtime trend views

[daniel-beck]

… time trend views

See JENKINS-72711.

Amends #8705

Testing done

Looked at the affected pages while builds were running while the previous build was: green, red, aborted, notbuilt, canceled.

Confirmed no other views include the responsible JS file (and would need these definitions).

Proposed changelog entries

• Restore progress animation in build history and build time trend views (regression in 2.434).

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

[mawinter69]

Not something for this PR but the many svg we include also blow up the html and usually most of them are not really needed (but one never knows). And I also have that in one of my plugins. So it would be nice to have the possibility to request a svg xml via fetch in javascript and just pass the symbol you want, e.g. <jenkinsurl>/symbol?name=symbol-star-outline plugin-ionicons-api
Or we provide directly a method and expose it to plugins.
getJenkinsSymbol("symbol-star-outline plugin-ionicons-api"), things like tooltip, htmltooltip, alt or id can be added as well

[NotMyFault]

Thanks!

[NotMyFault]

Not something for this PR but the many svg we include also blow up the html and usually most of them are not really needed (but one never knows). And I also have that in one of my plugins. So it would be nice to have the possibility to request a svg xml via fetch in javascript and just pass the symbol you want, e.g. <jenkinsurl>/symbol?name=symbol-star-outline plugin-ionicons-api Or we provide directly a method and expose it to plugins. getJenkinsSymbol("symbol-star-outline plugin-ionicons-api"), things like tooltip, htmltooltip, alt or id can be added as well

Possibly worth filing a dedicated issue linking this PR?

---

/label ready-for-merge

---

This PR is now ready for merge. We will merge it after ~24 hours if there is no negative feedback.
Please see the merge process documentation for more information about the merge process.
Thanks!