TEP-0077: Partial pipeline execute - wip - proposal.

teps/0077-pipeline-partial-execution.md

@@ -80,21 +80,40 @@ if this problem is solved?).
 
 ## Requirements
 
-<!--
-Describe constraints on the solution that must be met. Examples might include
-performance characteristics that must be met, specific edge cases that must
-be handled, or user scenarios that will be affected and must be accomodated.
--->
+- Create a new `PipelineRun` to resume or retry a completed `PipelineRun`.
 
 ## Proposal
 
-<!--
-This is where we get down to the specifics of what the proposal actually is.
-This should have enough detail that reviewers can understand exactly what
-you're proposing, but should not include things like API designs or
-implementation.  The "Design Details" section below is for the real
-nitty-gritty.
--->
+```yaml
+apiVersion: tekton.dev/v1beta1
+kind: PipelineRun
+metadata:
+  name: new-pipeline-run
+spec:
+  resumeFrom:
+    # can only be resumed from a previous PipelineRun
+    name: prev-pipeline-run
+    selectTasks:
+      # select tasks for which `pipelineRun.status.conditions` = False
+      conditions: False # either True|False|Unknown
+      # for selected tasks whether to clone results or not
+      cloneResults: True
+      disableTasks:
+        - name: task-name
+  serviceAccountName: 'default'
+  # Option1. these are cloned from previousRun and following specification
+  # overrides the cloned specs.
+  # Option2. disallow the following specification when resumeFrom exists
+  # and only use the specifications from previous run.
+  workspaces:
+  - name: some-data
+    persistentVolumeClaim:
+      claimName: some-storage
+  resources:
+  - name: repo
+    resourceRef:
+      name: some-ref
+```
 
 ### Notes/Caveats (optional)