|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-13230) Not able to use Jenkins ... [email protected] (JIRA)
- [JIRA] (JENKINS-13230) Not able to use Jen... [email protected] (JIRA)
- [JIRA] (JENKINS-13230) Not able to use Jen... [email protected] (JIRA)
- [JIRA] (JENKINS-13230) Not able to use Jen... [email protected] (JIRA)
- [JIRA] (JENKINS-13230) Not able to use Jen... [email protected] (JIRA)
- [JIRA] (JENKINS-13230) Not able to use Jen... [email protected] (JIRA)

I guess this relates to my request https://issues.jenkins-ci.org/browse/JENKINS-14340.
I see the need to resolve "natural" environment variables and parameters as more natural though since "Free style job" does it in a shell build step, and Publish Over SSH does not do it in "Send files or execute commands over SSH after the build runs".
Here is a easy job config.xml for reproducing the issue on 1.486 with publish over SSH 1.9:
echo echo "Build Step" echo "we have foo=${foo}" echo "we have bar=${bar}" echo "we have foobar=${foobar}"</command> </hudson.tasks.Shell> </builders> <publishers/> <buildWrappers> <jenkins.plugins.publish__over__ssh.BapSshPostBuildWrapper plugin="[email protected]"> <postBuild> <consolePrefix>SSH: </consolePrefix> <delegate> <publishers> <jenkins.plugins.publish__over__ssh.BapSshPublisher> <configName>TempArtifacts_deployer</configName> <verbose>false</verbose> <transfers> <jenkins.plugins.publish__over__ssh.BapSshTransfer> <remoteDirectory></remoteDirectory> <sourceFiles></sourceFiles> <excludes></excludes> <removePrefix></removePrefix> <remoteDirectorySDF>false</remoteDirectorySDF> <flatten>false</flatten> <cleanRemote>false</cleanRemote> <noDefaultExcludes>false</noDefaultExcludes> <makeEmptyDirs>false</makeEmptyDirs> <execCommand>#!/bin/bash echo echo "SSH deployer after the build runs" echo "we have foo=${foo}" echo "we have bar=${bar}" echo "we have foobar=${foobar}"</execCommand> <execTimeout>120000</execTimeout> <usePty>false</usePty> </jenkins.plugins.publish__over__ssh.BapSshTransfer> </transfers> <useWorkspaceInPromotion>false</useWorkspaceInPromotion> <usePromotionTimestamp>false</usePromotionTimestamp> </jenkins.plugins.publish__over__ssh.BapSshPublisher> </publishers> <continueOnError>false</continueOnError> <failOnError>false</failOnError> <alwaysPublishFromMaster>false</alwaysPublishFromMaster> <hostConfigurationAccess class="jenkins.plugins.publish_over_ssh.BapSshAlwaysRunPublisherPlugin" reference="../.."/> </delegate> </postBuild> </jenkins.plugins.publish__over__ssh.BapSshPostBuildWrapper> </buildWrappers> </project>The output of that job is