Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-10225

Pipeline Repository (Pipeline-as-Code) list page shows an empty Event type column

    XMLWordPrintable

Details

    • Moderate
    • ODC Sprint 233
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • NA

    Description

      Description of problem:
      Pipeline Repository (Pipeline-as-code) list never shows an Event type.

      Version-Release number of selected component (if applicable):
      4.9+

      How reproducible:
      Always

      Steps to Reproduce:

      1. Install Pipelines Operator and setup a Pipeline-as-code repository
      2. Trigger an event and a build

      Actual results:
      Pipeline Repository list shows a column Event type but no value.

      Expected results:
      Pipeline Repository list should show the Event type from the matching Pipeline Run.

      Similar to the Pipeline Run Details page based on the label.

      Additional info:
      The list page packages/pipelines-plugin/src/components/repository/list-page/RepositoryRow.tsx renders obj.metadata.namespace as event type.

      I believe we should show the Pipeline Run event type instead. packages/pipelines-plugin/src/components/repository/RepositoryLinkList.tsx uses

      {plrLabels[RepositoryLabels[RepositoryFields.EVENT_TYPE]]}

      to render it.

      Also the Pipeline Repository details page tried to render the Branch and Event type from the Repository resource. My research says these properties doesn't exist on the Repository resource. The code should be removed from the Repository details page.

      Attachments

        Issue Links

          Activity

            People

              viraj-1 Vikram Raj
              cjerolim Christoph Jerolimov
              Sanket Pathak Sanket Pathak
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: