When running a promotion I'd like to take advantage of env. saved in ../builds/$PROMOTED_NUMBER/injectedEnvVars.txt. Specifically, in the "Promote builds when" box, I'm using "Inject Environment Variables" action to inject above mentioned variables. I have a build parameter in a parameterized job that I need to get a hold of. I must get the parameter from the saved env. variables for that job. Hence my attempt to evaluate PROMOTED_NUMBER.
I know the variable is set because I created a SHELL build step before this, and echoed out the variables etc. As a work around I am copying the file into my workspace, then I don't have to use variables to refer to it in this "Inject Environement Variables" action.