Link outputSourceBindings from one PipelineTask to inputSourceBindings of next task

[nader-ziada]

Expected Behavior

A PipelineTask defined in a Pipeline yaml should link the output of one task to the input of the next task. For example a task to build and push a container image from source would pass that image along to the next task to deploy it.

apiVersion: pipeline.knative.dev/v1alpha1
kind: Pipeline
metadata:
  name: kritis-pipeline
  namespace: default
spec:
  tasks:
    - name: push-kritis              
      taskRef:
        name: build-push
      inputSourceBindings:
        - name: kritis-app-github
          key: workspace 
          resourceRef:
            name: kritis-repo-git
      outputSourceBindings:
        - name: kritisImage
          key: builtImage 
          resourceRef:
            name: kritis-resources-image
    - name: deploy-test-env           
      taskRef:
        name: deploy-with-helm
      inputSourceBindings:
        - name: kritisImage
          key: builtImage
          resourceRef:
            name: kritis-resources-image
          passedConstraints: [build-push]
      params:
        - name: pathToHelmCharts
          value: kritis-charts
      clusterBindings:
        - inputName: targetCluster
          key: testCluster

In this example, the builtImage resource created in the first task push-kritis (outputSourceBinding: kritisImage) should be passed along to the input of the deploy-test-env task as the inputSourceBinding (kritisImage)

Actual Behavior

input resources are not currently linked

Additional Info

• The taskRun controller should ensure the version that got created in the first task is consumed by the taskRun of the next task

[shashwathi]

/assign @shashwathi

[shashwathi]

I think #160 is implementing this.

[nader-ziada]

pr #160 doesn’t figure out how to move artifacts between task runs, it just makes sure the tasks respect the order based on the passed constraints

[shashwathi]

Need to address #173 before diving into this issue.

[shashwathi]

Related issue #124