Bug 2092920

Created attachment 1886112 [details]
screenshot from UI

Description of problem:

OpenShift Pipelines task can depend on each other by either explicitly specifying "runAfter" field or by using previous task's results. When task depends implicitly by using results, the pipeline preview chart is incorrect.


Version-Release number of selected component (if applicable):

4.10 (and probably all older)


How reproducible:

always


Steps to Reproduce:
1. Create a pipeline like this
apiVersion: tekton.dev/v1beta1
kind: Pipeline
metadata:
  name: pipeline-result
spec:
  tasks:
  - name: first
    taskSpec:
      results:
      - name: foo
      steps:
      - name: test
        image: registry.access.redhat.com/ubi8/ubi-minimal
        script: |
          echo "something very important" > $(results.foo.path)
          sleep 30
          echo "Done"
  - name: second
    params:
    - name: input
      value: $(tasks.first.results.foo)
    runAfter:
    - first
    taskSpec:
      params:
      - name: input
      steps:
      - name: test
        image: registry.access.redhat.com/ubi8/ubi-minimal
        script: |
          echo "$(params.input)"
  - name: third
    params:
    - name: input
      value: $(tasks.first.results.foo)
    taskSpec:
      params:
      - name: input
      steps:
      - name: test
        image: registry.access.redhat.com/ubi8/ubi-minimal
        script: |
          echo "$(params.input)"

2. Run this pipeline

Actual results:

Task "second" is correctly linked to "first" but "third" is a standalone task although it can only run after "first" finishes.


Expected results:

Both tasks "second" and "third" are linked similarly to "first", both run at the same time.


Additional info: