Spinnaker Pipeline SpEL Expressions: Difference between revisions
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
* https://spinnaker.io/docs/guides/user/pipeline/expressions/ | * https://spinnaker.io/docs/guides/user/pipeline/expressions/ | ||
* https://spinnaker.io/docs/reference/pipeline/expressions/ | * https://spinnaker.io/docs/reference/pipeline/expressions/ | ||
* https://docs.armory.io/armory-enterprise/spinnaker-user-guides/expression-language/ | |||
=Internal= | =Internal= | ||
* [[Spinnaker_Concepts#Pipeline_SpEL_Expressions|Spinnaker Concepts]] | * [[Spinnaker_Concepts#Pipeline_SpEL_Expressions|Spinnaker Concepts]] | ||
Revision as of 02:22, 24 March 2022
External
- https://spinnaker.io/docs/guides/user/pipeline/expressions/
- https://spinnaker.io/docs/reference/pipeline/expressions/
- https://docs.armory.io/armory-enterprise/spinnaker-user-guides/expression-language/
Internal
Overview
The Spinnaker pipeline expression language is based on Spring Expression Language (SpEL).
Accessing Pipeline Element State
A Tag set by a Trigger
The tag set by a trigger can be accessed with the following expression:
- image: "something/something-else:${trigger['tag']}"
The Judgement Value set by a Manual Judgement Stage
${ execution.stages.?[ name == '<stage-name>' ][0].judgementInput }
where <stage-name> should be replaced with the actual name of the Manual Judgement stage.