You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The text was updated successfully, but these errors were encountered:
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:
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:
The text was updated successfully, but these errors were encountered: