[
https://issues.jenkins-ci.org/browse/JENKINS-13096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gbois resolved JENKINS-13096.
-
Resolution: Won't Fix
I'm afraid EnvInject will not be able to resolve your issue.
EnvInject is able to
[
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 mu
[
https://issues.jenkins-ci.org/browse/JENKINS-13096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160441#comment-160441
]
gbois commented on JENKINS-13096:
-
Any update?
> should be able to use Jenk
[
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.
There
[
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
[
https://issues.jenkins-ci.org/browse/JENKINS-13096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160326#comment-160326
]
gbois commented on JENKINS-13096:
-
Did you try to inject variables after a SCM checkout?
Che
[
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: https://issues.jenkins-ci.org/browse/JEN
