[
https://issues.jenkins-ci.org/browse/JENKINS-13096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160545#comment-160545
]
Maddy Goss commented on JENKINS-13096:
--
In my case I have the following parameters I
[
https://issues.jenkins-ci.org/browse/JENKINS-13096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160441#comment-160441
]
gbois commented on JENKINS-13096:
-
Any update?
should be able to use
[
https://issues.jenkins-ci.org/browse/JENKINS-13096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160365#comment-160365
]
gbois commented on JENKINS-13096:
-
In my approach, Jenkins jobs should be independent.
[
https://issues.jenkins-ci.org/browse/JENKINS-13096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JENKINS-13096 started by gbois.
should be able to use Jenkins Environment Variables (JENKINS_HOME, WORKSPACE)
in the properties file path
Maddy Goss created JENKINS-13096:
Summary: should be able to use Jenkins Environment Variables
(JENKINS_HOME, WORKSPACE) in the properties file path
Key: JENKINS-13096
URL: