Spinnaker "trigger did not fire" from CI

A CI job pushed an image or called a webhook expecting Spinnaker to start a pipeline, but no execution appeared. The trigger exists but its constraints (tag regex, artifact match, or enabled flag) did not match the incoming event.

What this error means

CI reports success but Spinnaker shows no new execution. The pipeline's trigger is configured but never fires for the pushed image or webhook call.

Spinnaker

# CI pushed myorg/app:1.4.2 but no pipeline started.
# Trigger tag regex: ^v\d+\.\d+\.\d+$  (does not match "1.4.2")

Common causes

The trigger constraint does not match the event

A Docker tag regex, branch filter, or expected artifact on the trigger excludes the exact value CI sent, so nothing fires.

The trigger or pipeline is disabled

A disabled trigger or a disabled/locked pipeline silently ignores incoming events.

How to fix it

Match the trigger to what CI actually sends

Confirm the exact tag, branch, or artifact CI emits.
Adjust the trigger regex or artifact constraint to match it.
Enable the trigger and pipeline, then re-push from CI.

Spinnaker trigger config

# widen tag regex so 1.4.2 matches
^v?\d+\.\d+\.\d+$

Verify the webhook reached Echo

For webhook triggers, confirm the CI call hit the Gate webhook endpoint and that Echo received it with the expected source/type.

How to prevent it

Keep trigger regexes in sync with your CI tag/branch scheme.
Test the trigger with the exact payload CI produces.
Alert when an expected trigger produces no execution.