Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-8065

Improve Results performance by skipping incomplete runs storage

XMLWordPrintable

    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      Added flag: `disable_storing_incomplete_runs` If set to true, Runs will not be stored until they are complete. If false, Runs will be initially stored upon creation and continuously upserted until after they're deleted.
      ~~~
      ...
      options:
          deployments:
            tekton-results-watcher:
              spec:
                template:
                  spec:
                    containers:
                    - args:
                      - "--disable_storing_incomplete_runs=true"
                      name: watcher
                      resources: {}
      ~~~
      Show
      Added flag: `disable_storing_incomplete_runs` If set to true, Runs will not be stored until they are complete. If false, Runs will be initially stored upon creation and continuously upserted until after they're deleted. ~~~ ... options:     deployments:       tekton-results-watcher:         spec:           template:             spec:               containers:               - args:                 - "--disable_storing_incomplete_runs=true"                 name: watcher                 resources: {} ~~~
    • Enhancement
    • Done
    • Pipelines Sprint Crookshank 32

      Story (Required)

      Background (Required)

      TaskRuns and PipelineRuns are continously reconciled even if they aren't done. This increases load on watcher reconcilers and API server.

       

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      Add a flag in watcher to disable live collection of Run

      Dependencies

      <Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

      Acceptance Criteria (Mandatory)

      <Describe edge cases to consider when implementing the story and defining tests>

      <Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

              rh-ee-kbaig Khurram Baig
              rh-ee-kbaig Khurram Baig
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: