I want to load a properties file such as /opt/jenkins/${GIT_COMMIT}.properties.

If I define Properties File Path in "Prepare an environment for the run" then it is interpreted as a literal (which is unhelpful); however Properties File Path in "Inject environment variables" (i.e. as a build step) is interpreted correctly (i.e. the filename is dynamic).

Loading the properties file as a build step is a partial workaround, except that options such as "Load script and properties files from the master" are not presented at this stage.

It would be helpful if both "Properties File Path" fields interpreted variables in the filename.