| James E. Blair | eff5a9d | 2017-06-20 00:00:37 -0700 | [diff] [blame] | 1 | :title: Timer Driver |
| 2 | |
| 3 | Timer |
| 4 | ===== |
| 5 | |
| 6 | The timer driver supports triggers only. It is used for configuring |
| 7 | pipelines so that jobs run at scheduled times. No connection |
| 8 | configuration is required. |
| 9 | |
| 10 | Trgger Configuration |
| 11 | -------------------- |
| 12 | |
| 13 | Timers don't require a special connection or driver. Instead they can |
| 14 | simply be used by listing **timer** as the trigger. |
| 15 | |
| 16 | This trigger will run based on a cron-style time specification. |
| 17 | It will enqueue an event into its pipeline for every project |
| 18 | defined in the configuration. Any job associated with the |
| 19 | pipeline will run in response to that event. |
| 20 | |
| 21 | **time** |
| James E. Blair | 88e5388 | 2017-06-23 21:45:07 +0100 | [diff] [blame] | 22 | The time specification in cron syntax. Only the 5 part syntax is |
| 23 | supported, not the symbolic names. Example: ``0 0 * * *`` runs at |
| 24 | midnight. |