Details
-
Epic
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
parameterization of the declarative PipelineRun
-
False
-
None
-
False
-
To Do
-
KONFLUX-1450 - Improve fork workflow for common assets in Stone Soup including Devfiles, PaC
-
0
-
0%
Description
Epic Goal
- Provide a path for users to not use hardcoded strings in the declarative PipelineRun such that the PipelineRun is executable in a forked repository.
Why is this important?
- Enables users to be able to fork a source code repo with .tekton/ and be able to run the PipelineRun in their own environment ( OpenShift, StoneSoup )
Scenarios
See larger discussion in:
https://issues.redhat.com/browse/STONE-680
Acceptance Criteria (Mandatory)
- Scenario: User should be able to craft a PipelineRun that builds source code and pushes an image to user-specific image repository.
- Scenario: User should be able to craft a PipelineRun that works with multiple build contexts a mono-repo. ( This likely will need multiple Repository CRs which is acceptable for the scope of this work )
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions::
- ...
Done Checklist
- Acceptance criteria are met
- Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
- User Journey automation is delivered
- Support and SRE teams are provided with enough skills to support the feature in production environment
Attachments
Issue Links
- duplicates
-
-
- Closed
-
