-
Improvement
-
Resolution: Won't Fix
-
Minor
I keep my generic project configuration in a properties file which is in a project that is checked into SCM. I would like to be able to update that file in a parent job, and then consume it (via $WORKSPACE/projectname/global.properties). Currently, you have to use the full path to the properties file, which makes my configuration brittle.
- is duplicated by
-
JENKINS-34441 Accept Jenkins environment variable in properties file path
- Closed