Skipped tasks shown as pending

[larhauga]

Describe the bug

Pipelines with tasks that are skipped (like due to non master branch run) is observed to have the state of pending even though it has been skipped. This issue came to us from end-users, which did not understand why the task was still pending.

Expected behaviour

We expect the status of the skipped task to be Skipped; not Pending.

Steps to reproduce the bug

In this case we have a when condition, that skipps this task if branch is main or master.

...
    - name: promote
      runAfter:
      - mvn-build
      taskRef:
        kind: ClusterTask
        name: # taskname
      when:
      - input: $(params.gitbranchname)
        operator: in
        values:
        - master
        - main
...

Environment details

• Kubernetes Platform: EKS

• Kubernetes or OpenShift version: 1.21

• Install mode (if on OpenShift): no

• Cloud-provider/provisioner: EKS

• Versions:
  • Tekton Dashboard: 0.23.0
  • Tekton Pipelines: 0.31.0
  • Tekton Triggers: 0.18.0
• Install namespaces:
  • Tekton Dashboard: tekton-pipelines
  • Tekton Pipelines:
  • Tekton Triggers:

Additional Info

[AlanGreene]

Thanks for raising this issue @larhauga. We're currently considering a redesign of this page to improve display of a number of things including when expressions, retries, and more.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[AlanGreene]

This is something we'll be addressing as part of the PipelineRun details page redesign which is currently in progress. Freezing so it doesn't get auto closed.

/lifecycle frozen

[AlanGreene]

When we address this we should review tektoncd/pipeline#4829 and TEP-0103. This makes additional useful information available regarding the reason for a task being skipped.

[AlanGreene]

Hoping to revisit this soon. Related to #1445