It could be nice to augment the Step type with a timeout duration, after which time the step fails with some unique status/message.

To support this we could pass the timeout value to the entrypoint binary, which would start a timer when step execution starts, and stop executing and raise a timeout error if execution doesn't finish in time.

If this is interesting to people it should be a pr

Expected Behavior

I would like to look into creating an on-boarding guide for new users. The github documentation is very good and well-maintained but what I am hoping for is to find and address a quick win for the user so that they understand quickly what they can use the dashboard for. Something that when they first fire up the product they can see it in action.

Important note: I am not

Describe the bug
The steps described for the Event Source tutorial for Native eventing provide directions for deploying the cronjob source and check for created pods in the knativetutorial namespace, however no pods are created and looking at the logs for sources-controller I see the following error:

{"level":"error","ts":"2020-01-07T01:59:26.137Z","logger":"source-controller.cronjob-so

A guide with all the options on exposing EventListeners:

1. Using the default Ingress
2. Using Nginx Ingress
3. Using a system like knative/eventing

If we do a tkn pipeline ls we have the start, duration and status field.

while if we do a tkn task ls we only have an age :

It could be nice to homogenize this

Additional Info

I am looking for the bazel.yaml file being referenced in the tutorial under the the following command:

$ kubectl apply -f bazel.yaml
task.tekton.dev/bazel created

I am trying to work with the following nodejs project:

git clone -b v1 https://github.com/docker-training/node-bulletin-board

Thanks
Sohil

As per the pipelines at https://github.com/pipeline-hotel/example-pipelines/tree/master/triggers-resources/config - when pushing a git tag to my git repository the webhooks-tekton-git-branch field that is added to the payload body in the interceptor, decides to list my tag as a branch name.

This is because of the trigger template specifying the label: `webhooks.tekton.dev/gitBranch: $(params.

We need better "Getting started guide" for the tekton projects.

• They should be on the docs/ folder of each of those project (like docs/getting-started/…)
• Repositories to tackle
  • tektoncd/pipeline
  • tektoncd/triggers — the [existing one](https://github.com/tektoncd/triggers/tree/master/docs/gettin

We should have standardized yaml and markdown linters. In a few issues, there's been problems with different forms of linters conflicting with each other causing issues (e.g. tektoncd/triggers#323 uses prettier, which seems to conflict with what yamllint wants).

Leading candidate is prettier due to its popularity (35k+ stars on GitHub), support fo