[
https://issues.jenkins-ci.org/browse/JENKINS-13155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160481#comment-160481
]
Oleksandr Popov commented on JENKINS-13155:
-------------------------------------------
Ive both 1.455 and 1.456 - with old 1.36 plugin version it working fine,
however with 1.38 it is not. Could you please fix this.
Thanks in advance!
> Parameters are not working in EnvInject plugin 1.38
> ---------------------------------------------------
>
> Key: JENKINS-13155
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13155
> Project: Jenkins
> Issue Type: Bug
> Components: envinject
> Environment: EnvInject 1.38
> Jenkins 1.455 / 1.456
> Reporter: Oleksandr Popov
> Assignee: gbois
> Priority: Critical
> Attachments: env-inject-issue.png
>
>
> When you specify variables in "Inject environment variables to the build
> process" / "Properties File Path" section (as it is presented in attached
> screenshot) it does not resolves those variables:
> 13:45:46 [EnvInject] - Executing scripts and injecting environment variables
> after the SCM step.
> 13:45:46 [EnvInject] - [ERROR] - The given properties file path
> '${WORKSPACE}/${Branch}/***/Install/properties/dbschema.property' doesn't
> exist.
> 13:45:46 [EnvInject] - [ERROR] - [EnvInject] - [ERROR] - Problems occurs on
> injecting env vars as a build wrap: hudson.util.IOException2: remote file
> operation failed: /*****/*****/jenkins/workspace/[Job-name] at
> hudson.remoting.Channel@147ed19:*****************
> Had to revert to 1.36 version
--
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
