Details
-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: jclouds-plugin
-
Environment:Windows + SSHd using command prompt or powershell environment (e.g. BitVise SSH server)
-
Similar Issues:
Description
jclouds-plugin v2.8 provides support for copying slave.jar to a provisioned instance in a *nix style environment. If the SSHd environment is on a Windows slave and is using the command prompt or powershell environment, /tmp is not able to scp and execute the slave.jar file since /tmp is a valid path.
Adding a mechanism to indicate that the JCloud template is a Windows slave would allow for a different copy and execution path for the slave.jar.
Code changed in jenkins
User: Fero
Path:
jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsLauncher.java
jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsSlave.java
jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate.java
jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate/config.jelly
jclouds-plugin/src/test/java/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplateTest.java
http://jenkins-ci.org/commit/jclouds-plugin/07b49674bea852c0085e05151fa092990b14bbdc
Log:
Merge pull request #112 from mikefero/windows-images-2.8
JENKINS-31655Copying and executing slave.jar on Windows slaveCompare: https://github.com/jenkinsci/jclouds-plugin/compare/3daf0c2e3060...07b49674bea8