Chitrang Patel
Chitrang Patel
Prior to this, propagating parameters only skipped webhook validation for params defined in script. As a result, when users tried to propagate params to other fields like `args` or `command`,...
The verbosity of writing specifications in Tekton Pipelines is a common pain point that creates difficulties in getting-started scenarios. In addition, the verbosity leads to long specifications that are error-prone,...
Prior to this, propagating parameters only skipped webhook validation for params defined in script. As a result, when users tried to propagate params to other fields like `args` or `command`,...
In the return of the function [ExtractVariablesFromString](https://github.com/chitrangpatel/pipeline/blob/732aed55d75e4b1024b1cedbe8022e868925fd0e/pkg/substitution/substitution.go#L241-L275), the boolean variable is redundant with the string slice that's returned (i.e. the bool is just len(stringslice) > 0).
[Test](https://github.com/chitrangpatel/pipeline/blob/62f0f52a00b30876c13dedcc7db436080c28f462/pkg/reconciler/taskrun/taskrun_test.go#L2515) contains too much logic in it. This indicates that we might not be testing this at the right level. Instead, call Reconcile function and validate the expected output.
This proposal outlines what information is required to reproduce complete build instructions for taskruns. It also suggests where in the provenance to store this information.
While working on PR https://github.com/tektoncd/pipeline/pull/6072, I noticed that 5 `alpha` [integration tests](https://prow.tekton.dev/view/gs/tekton-prow/pr-logs/pull/tektoncd_pipeline/6072/pull-tekton-pipeline-alpha-integration-tests/1620184025870110720) were skipped. Of the five, two were because they require `embedded-status: full` and `enable-provenance-in-status: true`. However, the kind-e2e...
### Feature request Today, users generally declare workspaces for sharing data between `Steps` in a `TaskRun`. Tekton provides some implicit volume mounts that users are probably unaware of due to...
Just like we have Trusted Tasks and Pipelines, we should probably also have `Trusted StepActions`. cc @jerop @Yongxuanzhang WDYT?
Tekton Pipelines introduced `StepActions` in [v0.54.0](https://github.com/tektoncd/pipeline/releases/tag/v0.54.0). We want to provide a catalog of Tekton `StepActions` and host them on ArtifactHub like we do for Tekton `Tasks` and `Pipelines`. What would...