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

Unnecessary API calls if TektonConfig is not minimal

XMLWordPrintable

    • Moderate
    • No
    • ODC Sprint 3246
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None

      This is a clone of issue OCPBUGS-13152. The following is the description of the original issue:

      Description of problem:
      With OCPBUGS-11099 our Pipeline Plugin supports the TektonConfig config "embedded-status: minimal" option that will be the default in OpenShift Pipelines 1.11+.

      But since this change, the Pipeline pages loads the TaskRuns for any Pipeline and PipelineRun rows. To decrease the risk of a performance issue we should make this call only if the status.tasks wasn't defined.

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

      • 4.12-4.14, as soon as OCPBUGS-11099 is backported.
      • Tested with Pipelines operator 1.10.1

      How reproducible:
      Always

      Steps to Reproduce:

      1. Install Pipelines operator
      2. Import a Git repository and enable the Pipeline option
      3. Open the browser network inspector
      4. Navigate to the Pipeline page

      Actual results:
      The list page load a list of TaskRuns for each Pipeline / PipelineRun also if the PipelineRun contains the related data already (status.tasks)

      Expected results:
      No unnecessary network calls. When the admin changes the TektonConfig config "embedded-status" option to minimal the UI should still work and load the TaskRuns as it does it today.

      Additional info:
      None

              viraj-1 Vikram Raj
              openshift-crt-jira-prow OpenShift Prow Bot
              Sanket Pathak Sanket Pathak
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: