cli
cli copied to clipboard
tektoncd
Make tkn easier to automate: add run name output, add status check
Version and Operating System
tkn Version: 0.8.0
Expected Behavior
I want to automate task/pipeline runs with tkn. So i want to be able to do smth like
run_name=$(tkn p start -o name pipeline_name)
tkn pr logs -f $run_name
exit $(tkn pr status $run_name)
or shorter
tkn p start --showlog --watch pipeline_name
So it would be nice to add:
- option "only output a name of new created run" to run command
- status command to find out how run ended
- optionally: add "watch and exit with run status" option to run command
I know that i now can get all data from pipeline run body, but name/status fields seem to be standard enough to deserve separate call in command line.
(I guess tkn version is 0.8.0 though, and the pipeline instance is 0.10.x)
/kind feature
Even tho that doesnt address fully your use case there is the --last option as well..
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.
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.
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: 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.
@vdemeester: Reopened this issue.
In response to this:
/remove-lifecycle rotten /remove-lifecycle stale /reopen
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.
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.
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.
Yeah i think there was a PR floating around about it, we need to check how to revive this.
+1 on this feature.
Today we are using the following script
tkn pr describe $run_name -o json | jq -c '.status.conditions[] | select(.type | contains("Succeeded")?) | .status'
Yeah i think there was a PR floating around about it, we need to check how to revive this.
@chmouel are you referring to this PR https://github.com/tektoncd/cli/pull/1433 (but for the name, not the status)?
