[
https://issues.jenkins-ci.org/browse/JENKINS-13096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160338#comment-160338
]
Maddy Goss commented on JENKINS-13096:
--------------------------------------
actually, in this one instance, I am injecting environment variables prior to
the scm checkout. (I use it to determine the specific scm revision to check
out). ie:
* parent project/job - checks out the configuration containing the desired scm
revision number
* child projects/jobs - load the configuration pre-scm and use it to specify
the revision being checked out
Hope that helps :)
> 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
