Hello,

I'm reporting it first in config-file-provider-plugin since the issues is reproducible by using config-file-provider-plugin

Note that, as the token-macro version is the culprit, the issue lies within

• the combination of config-file-provider-plugin and token-macro
• or
• only token-macro

To reproduce

Note that the issue was also reproduced in a pipeline build with configFileProvider(...)

• Jenkins 2.340
• Config-file-provider-plugin 3.9.0 (latest at the moment of writing these lines)
• token-macro plugin 285.vff7645a_56ff0 (latest at the moment of writing these lines)
• Steps (Screenshots for each step below)
  • Create a custom managed file with tokens.
    1. Put

as the file contents with tokens.
Doesn't matter what the tokens are, it just need to be activated. Token must not be one of the strings contained in the config file.

• • Create an empty Freestyle Build
    1. Use this managed file so it's available in the workspace
  • Run the build, go to the workspace files and
    1. See the managed file is now this with additional characters.

To reproduce without the issue

• Jenkins 2.340
• Config-file-provider-plugin 3.9.0
• token-macro plugin 267.vcdaea6462991. I haven't tried with versions between 267[   and   ]285

Workaround

Avoid usage of dollar sign $. However, it's not possible in all cases.**