Uploaded image for project: 'Docs for Red Hat Developers'
  1. Docs for Red Hat Developers
  2. RHDEVDOCS-5316

Support in CLI for TektonResults

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • OpenShift Pipelines
    • devex docs #240 Jun 15-Jun 29, devex docs #241 Jun 29-Jul 13, devex docs #242 Jul 13-Jul 27, devex docs #243 Jul 27-Aug 10, devex docs #244 Aug 10-Aug 25, devex docs #245 Aug 24-Sep 13, devex docs #246 Sep 14-Oct 5, devex docs #247 Oct 5-Oct 26, devex docs #248 Oct 26-Nov 16, devex docs #249 Nov 16-Dec 7, devex docs #250 Dec 7-Dec 28, devex docs #251 Jan 2-Jan 23, devex docs #252 Jan 23-Feb 12, devex docs #253 Feb 12-Mar 4
    • 5
    • Documentation (Ref Guide, User Guide, etc.), User Experience
    • Added commands for Logging in tkn-results integrated in opc.
    • ---
    • ---

      Story (Required)

      Tekton CLI should support Record, List and Log feature of Tekton results
      As a <PERSONA> trying to <ACTION> I want <THIS OUTCOME>

      <Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

      Background (Required)

      At present, there's a separate cli which isn't maintained and also behaves in much different way from normal cli. We need a cli client to get log and metadata of pipelineruns and taskruns saved in results.
      <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

            mramendi Mikhail Ramendik
            mramendi Mikhail Ramendik
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: