Make Pipeline task name available in Task/ClusterTask

[dinup24]

The pipeline task name set in the pipeline definition should be made available in the task as internal param or env variable (or in some other way) during execution. The steps/sidecar in the task should be able to use the pipeline task name which could be useful logging/tracing/debugging purposes.

tasks:
  - name: build-the-image
    taskRef:
      name: build-push

In the above example pipeline task name is build-the-image, but it invokes the task build-push. If certain contextual info such as the pipeline task name, pipeline name etc is made available in the task build-push , this will be helpful in understanding the context in which this task was executed (in our case, the same task is executed multiple times in a pipeline to perform same activities for different set of artifacts).

For eg. build-push task will be used to push ui-app image as well api-server image.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
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.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[bobcatfish]

This may have been somewhat solved by #1522 (thanks @R2wenD2 !)

You can now access variables like the pipelinerun name and the pipelinename in the pipeline - to make these available to a Task/ClusterTask it could declare them as params.