Spinnaker trigger expressions do not work with Harness Jenkins triggers

Spinnaker trigger expressions do not work with Harness Jenkins triggers

TL;DR

Migrating from Spinnaker to Harness: Jenkins trigger payload expressions will not carry over, because Harness Jenkins triggers cannot receive payloads. Plan on a custom webhook trigger and pass the values (hash, branch) in the webhook body. Context: From the Harness Spinnaker migration prerequisites guide.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

Spinnaker expressions that read Jenkins trigger payloads, like the trigger properties hash expressions, have no equivalent in a Harness Jenkins trigger, which does not natively support passing payloads. The documented workaround is to switch to a custom webhook trigger and POST the payload yourself, then read it from the webhook payload instead.

Source: From the Harness Spinnaker migration prerequisites guide. Spinnaker expressions that read Jenkins trigger payloads, like the trigger properties hash expressions, have no equivalent in a Harness Jenkins trigger, which does not natively support passing payloads. The documented workaround is to switch to a custom webhook trigger and POST the payload yourself, then read it from the webhook payload instead.

Verified resolution: Migrating from Spinnaker to Harness: Jenkins trigger payload expressions will not carry over, because Harness Jenkins triggers cannot receive payloads. Plan on a custom webhook trigger and pass the values (hash, branch) in the webhook body.

Source URL: https://github.com/harness/migrator/blob/HEAD/docs/docs/spinnaker-migration/prerequisites.md