Aha, I found an (alternative) simple solution! In the job config...
*Build Environment*
X Inject environment variables to the build process
Properties File Path C:\pathtofile\mapping.properties
Properties Content THEME_NAME=${${PROJECT_NAME}}
Thanks Eric for your reply that led me to the idea.
O
In bash you could do something like this. Let's assume you have the
property file mapping.properties in the workspace, and the user chose
proj1 as the value of PROJECT_NAME.
. mapping.properties
echo ${!PROJECT_NAME}
or alternatively:
eval THEME_NAME=\$$PROJECT_NAME
Thanks to http://tldp.org/
I asked this in StackOverflow but thought this might be a more targeted
place to get an answer...
I have a parameterized job where I need to set an environment variable
based on a choice parameter the user chooses. Each project has a theme
project dependency. I'd like to have the user choose th
