-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
Pipelines Sprint Crookshank 35, Pipelines Sprint Crookshank 36, Pipelines Sprint Crookshank 37, Pipelines Sprint Crookshank 38
Story (Required)
Currently, finalizers in Results, Chains and PaC are managed using Merge Patches + resourceVersion check. Because of that check and multiple controllers updating the same types of objects (TaskRun and PipelineRun), many times the update fails because the object is updated by another client/controller, leading to many re-tries.
With Server-Side Apply, each controller can manage their own finalizer, without conflicts and without re-tries. Currently all controllers use functionality exposed by Pipelines to the change to support Server-Side Apply patches should be first added there and then start switching all controllers to make use of this new functionality.
This story is about adding the functionality in Pipelines.
Background (Required)
<Describes the context or background related to this story>
Out of scope
Updating Results/Chains/PaC to use Server-Side Apply patches. Those will be separate stories.
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