Design for cron triggering about triggers HOT 5 CLOSED

Considering our current design is focused around HTTP requests, and all events don't necessarily come in that format, my understanding is that we will eventually end up having a separate event-adapter library (or will recommend lightweight adapter(s) that already exist; for example vincent's github adapter).

With this in mind, I think the best way to approach this is to have an adapter that will produce an HTTP event or CloudEvent when the cronjob is supposed to execute. Knative eventing has something similar here, although it isn't as light on dependencies as we would like.

from triggers.

Agree with @EliZucker , this part should not in the scope of Trigger.
Any reason we don't leverage Knative eventing or Knative contrib? not light enough?
if so i guess we need consider to create tekton's event source repo.

from triggers.

The solution could be that we recommend Knative eventing, I don't want to jump to any conclusions just yet!

Basically if I wanted to use Tekton as a complete CI solution (and I do! :D tektoncd/pipeline#267) then I would need to be able to setup cron triggering somehow. And if I found the "triggering" part of the project but found no guidance about how to setup triggering based on the passage of time (i.e. cron) I'd be very frustrated.

So this issue is just to track that at the very least we should have docs to help users set this up - but we should also do some investigation and make sure we're happy with whatever we suggest (and decide what and if we want to implement anything ourselves).

from triggers.

One thing we could do is recommend third party sources such as Google Cloud Scheduler, or easy cron.

also, you can declare cron jobs within Kubernetes.

I wouldn't mind taking a stab at it

from triggers.

Closing for now thanks to #162

from triggers.