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

Multiple CheckRun when the first checkrun has failed

XMLWordPrintable

    • 5
    • Pipelines Sprint 255, Pipelines Sprint 256, Pipelines Sprint 257, Pipelines Sprint Pioneers 2, Pipelines Sprint Pioneers 3, Pipelines Sprint Pioneers 4, Pipelines Sprint Pioneers 5, Pipelines Sprint Pioneers 6

      Story (Required)

       

      When there is an issue with a pipelinerun in .tekton/ when PaaC cannot parses it, PaaC will create a check run with an error message looking like this:

       

      Pipelines a Code CI - Failed

       

      when you fix that error it will create a new one:

       

      Pipelines as Code CI / pipeinerun-foo - Running

       

      the problem is that the first one should get cleared.

       

      We should either make sure the old ones get cleared or add a gitops comment for this to be able to clear the status

      Background (Required)

      <Describes the context or background related to this story>

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      <Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

      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

              sashture Savita .
              cboudjna@redhat.com Chmouel Boudjnah
              abdeljawed khelil abdeljawed khelil
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: