tektoncd
Explaining the relation between "Command", "Args" and "Script" in Tekton Steps
Hello there, I am new to Tekton and at the moment I am trying to understand the step syntax inside of tasks. It seems like there are three different keywords that can be used inside a single step: "command", "args" and "script". The documentation (https://tekton.dev/docs/pipelines/tasks/) is very detailed in explaining the "script" keyword but I can not find Info on how the other two work.
The only thing I could find on the web was this resolved Issue: https://github.com/tektoncd/pipeline/issues/781 and this short blog: https://medium.com/my-engineering-notes/task-step-from-command-to-script-88f6bec9ac26
I would be happy to have a more detailed documentation on Tekton Steps.
The step is built on top of the Kubernetes container spec, so the command and args fields are those provided by Kubernetes, i.e. command is similar to the Docker entrypoint
https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#define-a-command-and-arguments-when-you-create-a-pod
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.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
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 rotten
Send feedback to tektoncd/plumbing.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/close
Send feedback to tektoncd/plumbing.
@tekton-robot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopenwith a justification. Mark the issue as fresh with/remove-lifecycle rottenwith a justification. If this issue should be exempted, mark the issue as frozen with/lifecycle frozenwith a justification./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.