Thanks to the magic in the code, it appears EnvInject can contribute env vars to script steps in Pipeline. However, Durable Task 1.13 breaks some use-cases like nested variables (e.g. "MYVAR=$MYVAR:123" see the changelog).

• EnvInject really injects job properties in this case using some non-trivial logic. I didn't notice that routine during the code review
• Upgrade to Durable task 1.13 breaks the use-case
• Upgrade to "Pipeline Nodes and Processes Plugin" 2.10 does not resolve the issue

Though EnvInject does not support Pipeline, the root cause of this issue needs to be investigated and maybe fixed. Likely the fix should be applied on the EnvInject side according to my initial investigation.