Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build summary UI view #2287

Open
hk-vmg opened this issue Nov 30, 2020 · 1 comment
Open

Build summary UI view #2287

hk-vmg opened this issue Nov 30, 2020 · 1 comment

Comments

@hk-vmg
Copy link
Contributor

hk-vmg commented Nov 30, 2020

What happened:
When a build completes (success or fail), it requires multiple clicks to find results.

For example, if a build fails, I go to the UI for my pipeline, then click the event, then click the failed build bubble, then hope that the last message in the highlighted step is a relevant error.

It is roughly possible to do this with event label, but that UI element does not wrap or hover, so only a very short string <18 chars is visible, and it's per event not per build.

What you expected to happen:
It would save a lot of time for users if template authors or pipeline authors could specify simple messages, or possibly more complex data, to be shown at a per-build level.

For example, one possibility would be a box shown when hovering over a green/red build bubble which displayed key/value data from a new sub-item from meta.
Another way to do this could be an extra box at the top of the build event page.

This box could be used to show things like:

  • artifact version
  • error message(s)
  • links to relevant documentation or other related systems such as monitoring or the URL of a deployed artifact

It could be a generic place to include existing data like code coverage as well, so the UI does not need to get more cluttered.

In an ideal world, there could be a summary for either the build and/or the event.

How to reproduce it:

@tkyi tkyi added the ui label Jan 19, 2021
@tkyi tkyi added the feature label May 25, 2021
@tkyi
Copy link
Member

tkyi commented Nov 13, 2024

Might be related to #2880

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants