Vincent Demeester
Vincent Demeester
Signed-off-by: Vincent Demeester
The idea is to mimic running a `PipelineRun` with a `ServiceAccount` that has some secrets attach. The idea is that setting this would make all steps to have a `/tetkon/home/…`...
As of today, using `plain` output (default when no tty) is relatively verbose and hard to read. We could do something closer to dagger's output instead: 
Make it possible to pass arguments to the build. This would be useful for: - Overidding PipelineRun parameters - Pass secrets, configmap, … - Pass options to the frontend -...
Make sure we take into account `PodTemplate` when running Pipelines and Tasks
As a non-required check, to see the progress of "support" 😝
If we see a `CustomTask` (in a `Pipeline`) how should we *act* ? Should we support some (matrix, …) or just error out ?
Create some documentation around how to use `buildkit-tekton` with docker, or buildkit itself, as well as options, shortcomings, …
Support all the thing we can support from ContainerSpec