Pipeline with one task - experimental

[pxp928]

Current Behavior

Currently we use various Tekton tasks from the catalog or generated our own to create a complete build/publish pipeline. Could we create a pipeline with one task to build, test, scan and publish instead of using multiple?

This would all us to capture the attestation for the entire pipeline in one task. This would also ensure that materials used in the task created the product as they do not need to be shared between tasks.

Expected Behavior

Create a task with multiple steps to account for the build, test, scan, publish...etc. of a pipeline. What are the limitations of creating such a large task? Is it feasible and does it add value?