[
https://issues.jenkins-ci.org/browse/JENKINS-13096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160545#comment-160545
]
Maddy Goss commented on JENKINS-13096:
--------------------------------------
In my case I have the following parameters I must follow:
1) All configuration must be checked into SCM - Therefore I must start off my
build cycle with a job that updates the configuration project in the workspace.
2) All projects (jobs) in our (Nightly) build sweep must checkout and use a
single SVN revision. (This is to avoid mid-sweep check-in issues) - Therefore
I'm using the EnvInject to load a property file with the desired scm revision
and using that in the scm configuration (ie
http://repo/trunk/project@$revision_property)
In order to support this, I need to be able to load the properties file from
the workspace (ie $WORKSPACE/globalConfigProject/scm_revision.properties) or at
least relative to jenkins home ($JENKINS_HOME/<relative path to
workspace>/globalConfigProject/scm_revision.properties). This way I can run the
build on any jenkins server node on any host os without having to know the
absolute path to the properties file.
Oh and to answer your question, I'm using the "Build other projects" post build
action to kick off the downstream build jobs (from the configuration update
job).
Hope that helps! :)
Maddy
> 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
