-
Story
-
Resolution: Won't Do
-
Critical
-
None
-
None
-
False
-
None
-
False
-
-
Story (Required)
As a user trying to get logs of the pipelineruns, I want to see logs of the pipelinesruns created by the results
Background (Required)
<Describes the context or background related to this story>
Uptil now user can only see logs of the pipelineruns present in cluster but there is a usecase to show logs of a pipelineruns created by the results
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>
By default opc pipelineruns logs should show logs of pipelineruns from cluster and from the results.
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>
opc pipelinrun logs => should provide logs of pipeline runs in the results and the cluster
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
- clones
-
SRVKP-5635 opc pipelineruns list should also show pipelineruns from the result
- Closed
- is cloned by
-
SRVKP-5637 opc pipelineruns describe should also be able to describe the pipelineruns from the results
- Closed