git-set-commit-status task fails when pipeline triggered from non-SCM trigger about tekton-catalog

[jauninb]

@nastacio can you be more specific on the use-case you are trying to achieve ?
This task is expecting to set a commit status on a given revision/commit id
The commit id can be given as a parameters using the revision param - see

tekton-catalog/git/task-set-commit-status.yaml

Line 29 in 764b973

- name: revision

If your goal is to skip a given task invocation in your tekton pipeline according to the trigger, maybe condition can help or a refine of the tekton pipeline flow

[nastacio]

@nastacio can you be more specific on the use-case you are trying to achieve ?
This task is expecting to set a commit status on a given revision/commit id
The commit id can be given as a parameters using the revision param - see

tekton-catalog/git/task-set-commit-status.yaml

Line 29 in 764b973

- name: revision

If your goal is to skip a given task invocation in your tekton pipeline according to the trigger, maybe condition can help or a refine of the tekton pipeline flow

More specific: if you put the current task in a pipeline, the task will fail when the pipeline is invoked with a manual trigger.
With this small modification, it does not.

I know every user can eventually bump into the problem and realize they can add a condition to avoid running the task, but the suggestion here would save people a lot of time without detracting from the purpose of the sample.

[ejodet]

PR #119

[jauninb]

This task can be invoked from non SCM Git trigger pipeline if the commit is provided using git-clone task output for instance - in case of manual run
Preventing this in the task implementation is not appropriate
Closing this issue