Question: Multiple triggers, listeners

[adjavaherian]

So, Without any sort of conditionals in the trigger templates, what is the current recommendation for assigning different pipelines to different event types?

For example, on PRs, I want to have a full build => deploy pipeline for a preview environment.
But for a commit to a dev branch, I simply want to build an artifact (to be deployed in a separate process).

Do you all do this with multiple triggers now? This seems to be overkill, considering that each trigger requires an ingress and listener and hook too. Any suggestions?

[ncskier]

The current way to get around this is to have your interceptor decide whether or not to run the trigger. For your example, you would pass an argument for the branch into the interceptor's header; more info in docs here, and an example interceptor here.

Also, please check out issue #49 about adding filtering to the triggers. The issues discusses how to make these common filtering operations becomes easier to configure. Do you think this issue addresses your concerns?

[dibyom]

Filters should be in the upcoming 0.2 release. Until then, the workaround would be to use a interceptor as @ncskier mentioned.