liveBook · Manning

Event-based trigger

As explained in Effective Platform Engineering

An event-based trigger starts an automation process in response to a defined event rather than an operator manually initiating it.

An event-based trigger starts a pipeline when a defined event occurs instead of relying on an operator to initiate it. This supports predictable continuous-deployment automation by preserving a known event order. section 6.2.2

Apply the pattern with these constraints:

  • Treat manually triggering a pipeline inside the pipeline tool as an anti-pattern rather than a normal operating path. section 6.2.2
  • Reserve tool-initiated triggering primarily for retries, while allowing defined events to drive normal execution. section 6.2.2
  • Protect confidence in deployment automation by keeping expected events in a specific order. section 6.2.2

How Effective Platform Engineering covers it

How deep it goes
Explains the trigger policy and its relationship to ordered automation, but does not specify event schemas or implementation configuration.
Examples
Uses normal event-driven pipeline execution and manually initiated retries as contrasting operating paths.
What you can do after
Evaluate pipeline-trigger designs by checking event ordering and isolating manual initiation to retries.
How it connects
Connects event-based triggers with pipelines, retries, continuous deployment, and automation confidence.

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.