Uploaded image for project: 'Konflux UI'
  1. Konflux UI
  2. KFLUXUI-117

Commit status is based on build pipeline only, issues with related pipelines aren't surfaced until clicking into one

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Konflux

      The status we show when listing commit information comes from the build pipeline. Failures in related pipelines that were triggered with the build finishing aren't reflected until a user views the commit details page, or looks at the un-aggregated pipeline runs elsewhere.

      Can status better reflect the chain of events triggered by a commit? If not, can we make it more clear which status is summarized there?

      https://redhat-internal.slack.com/archives/C04PZ7H0VA8/p1695829895516609

              Unassigned Unassigned
              mreid1@redhat.com Matt Reid
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: