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

Add tkn cli support to rerun an existing resolver based PR (remote resolution support)

XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      This introduces a new flag called `--resolvertype`. This flag allows users to specify the resolver type (such as `git`, `http`, `hub`, `cluster`, `bundle`, and a special type `remote` resolvers (which would be any supported type resolver)) when re-running a resolver-based pipeline.
      Show
      This introduces a new flag called `--resolvertype`. This flag allows users to specify the resolver type (such as `git`, `http`, `hub`, `cluster`, `bundle`, and a special type `remote` resolvers (which would be any supported type resolver)) when re-running a resolver-based pipeline.
    • Feature
    • Proposed
    • Pipelines Sprint Crookshank 32, Pipelines Sprint Crookshank 33, Pipelines Sprint Crookshank 37, Pipelines Sprint Crookshank 38, Pipelines Sprint CrookShank 39, Pipelines Sprint CrookShank 40, Pipelines Sprint CrookShank 41

      Story (Required)

      upstream issue https://github.com/tektoncd/cli/issues/2422

      CLI option to rerun a resolver based pipelinerun

      As a CLI user I want to be able to rerun a resolver based pipelinerun simply by referencing an existing pipelineRun name

      UI Example

      $ tkn pipelinerun rerun <pipelinerun-name>

      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

              shverma Shiv Verma
              rbehera-1 Rupali Behera
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: