[
https://issues.jenkins-ci.org/browse/JENKINS-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161768#comment-161768
]
bap commented on JENKINS-13460:
-------------------------------
If you use a vaiable in the global config, I can then set that variable to
anything I want in the job configuration.
This exactly what you are trying to avoid!
> Environment variables not explanded for "Remote Directory" configuration
> ------------------------------------------------------------------------
>
> Key: JENKINS-13460
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13460
> Project: Jenkins
> Issue Type: Bug
> Components: publish-over-ssh
> Reporter: Bertrand Latinville
> Assignee: bap
> Priority: Minor
> Labels: deployment, plugin
>
> I'm using publish over ssh to send file on a remote folder
> and Exec commands.
> As the folder where I put the files may change in the future I defined a
> Jenkins environment variable: REMOTE_LOCATION.
> I'd like to use this variable in SSH publish over configuration and in the
> Exec command of the job.
> I configured ssh publish over plugin with Remote Directory set to
> ${REMOTE_LOCATION}
> I get this error :
> ERROR: Exception when publishing, exception message [Failed to change to
> remote directory [${REMOTE_LOCATION}]]
> Build step 'Send build artifacts over SSH' changed build result to UNSTABLE
> I checked that the variable is set properly by echo ${REMOTE_LOCATION} in the
> Exec command.
> Variables should be expanded in the "Remote Directory" configuration field.
--
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
