-
Story
-
Resolution: Unresolved
-
Major
-
None
-
Pipelines 1.14.4
-
8
-
False
-
None
-
False
-
-
Story (Required)
When doing a /test, /retest or a custom gitops command I would like to be able to redefine pipelines as code parameters (custom or standard) from my github command.
Example:
/test pipelinerun1 key=value revision=otherrevision
Acceptance Criteria (Mandatory)
This applies only to the templates parameters (the one inside the {{ }}) and not to CEL expression.
CEL expressions inside template parameters should be handle properly from the redefined values.
Background (Required)
Customer:
For our use case that's really important because we have hundreds of test suites where we would want to run only one or a few by passing in a param.
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.>
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