[ https://issues.jenkins-ci.org/browse/JENKINS-13096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160365#comment-160365 ]
gbois commented on JENKINS-13096: --------------------------------- In my approach, Jenkins jobs should be independent. Therefore, file paths in 'Prepare job environment' section must be absolute. Your need is a pipeline (or build chain) issue. And you need to propagate your scm revision. I don't have a solution at the moment. I'm looking for an alternative. Could let me know how jobs are tied? (do you use upstream/downstream feature, the parameterized job parameter or the build result trigger plugin)? > should be able to use Jenkins Environment Variables (JENKINS_HOME, WORKSPACE) > in the properties file path > --------------------------------------------------------------------------------------------------------- > > Key: JENKINS-13096 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13096 > Project: Jenkins > Issue Type: Improvement > Components: envinject > Affects Versions: current > Reporter: Maddy Goss > Assignee: gbois > Priority: Minor > Labels: plugin > > 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira