job blocks

[drewbanin]

Presently, dbt runs in a monolithic fashion. The entire graph, or some subgraph thereof, is executed from beginning to end when dbt run is invoked.

dbt should provide a mechanism to define "orchestrations" of jobs which select models to run, apply configurations, attach hooks, and run arbitrary sql.

[drewbanin]

This is a good idea, but "job blocks" (ie. jinja code) is not the right way to orchestrate dbt runs. See #594 for more developed thinking on this topic.