[JIRA] (JENKINS-38269) Make vSphere cloud slave template's launcher and retention fields configurable
Title: Message Title pjdarton updated JENKINS-38269 Jenkins / JENKINS-38269 Make vSphere cloud slave template's launcher and retention fields configurable Change By: pjdarton Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38269) Make vSphere cloud slave template's launcher and retention fields configurable
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38269 Re: Make vSphere cloud slave template's launcher and retention fields configurable Code changed in jenkins User: Jason Swager Path: src/main/java/org/jenkinsci/plugins/RunOnceCloudRetentionStrategy.java src/main/java/org/jenkinsci/plugins/vSphereCloudSlaveTemplate.java src/main/java/org/jenkinsci/plugins/vsphere/RunOnceCloudRetentionStrategy.java src/main/java/org/jenkinsci/plugins/vsphere/VSphereCloudRetentionStrategy.java src/main/resources/org/jenkinsci/plugins/vSphereCloud/config.jelly src/main/resources/org/jenkinsci/plugins/vSphereCloudSlave/help-launchDelay.html src/main/resources/org/jenkinsci/plugins/vSphereCloudSlaveTemplate/config.jelly src/main/resources/org/jenkinsci/plugins/vSphereCloudSlaveTemplate/help-forceVMLaunch.html src/main/resources/org/jenkinsci/plugins/vSphereCloudSlaveTemplate/help-launchDelay.html src/main/resources/org/jenkinsci/plugins/vSphereCloudSlaveTemplate/help-launcher.html src/main/resources/org/jenkinsci/plugins/vSphereCloudSlaveTemplate/help-limitedRunCount.html src/main/resources/org/jenkinsci/plugins/vSphereCloudSlaveTemplate/help-retentionStrategy.html src/main/resources/org/jenkinsci/plugins/vSphereCloudSlaveTemplate/help-waitForVMTools.html src/main/resources/org/jenkinsci/plugins/vsphere/RunOnceCloudRetentionStrategy/config.jelly src/main/resources/org/jenkinsci/plugins/vsphere/VSphereCloudRetentionStrategy/config.jelly src/main/resources/org/jenkinsci/plugins/vsphereCloudProvisionedSlave/help-launchDelay.html src/test/java/org/jenkinsci/plugins/vsphere/tools/CloudProvisioningAlgorithmTest.java src/test/java/org/jenkinsci/plugins/vsphere/tools/CloudProvisioningStateTest.java http://jenkins-ci.org/commit/vsphere-cloud-plugin/f5c2d4ca707d5312320f7ffe8f19ab4a5795c094 Log: Merge pull request #54 from pjdarton/implement_jenkins_38269 Implement JENKINS-38269 Compare: https://github.com/jenkinsci/vsphere-cloud-plugin/compare/8971edf3a5ee...f5c2d4ca707d Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38269) Make vSphere cloud slave template's launcher and retention fields configurable
Title: Message Title pjdarton updated JENKINS-38269 Jenkins / JENKINS-38269 Make vSphere cloud slave template's launcher and retention fields configurable Change By: pjdarton Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38269) Make vSphere cloud slave template's launcher and retention fields configurable
Title: Message Title pjdarton commented on JENKINS-38269 Re: Make vSphere cloud slave template's launcher and retention fields configurable Implemented in https://github.com/jenkinsci/vsphere-cloud-plugin/pull/54 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38269) Make vSphere cloud slave template's launcher and retention fields configurable
Title: Message Title pjdarton started work on JENKINS-38269 Change By: pjdarton Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38269) Make vSphere cloud slave template's launcher and retention fields configurable
Title: Message Title pjdarton created an issue Jenkins / JENKINS-38269 Make vSphere cloud slave template's launcher and retention fields configurable Issue Type: Improvement Assignee: pjdarton Components: vsphere-cloud-plugin Created: 2016/Sep/16 10:54 AM Priority: Minor Reporter: pjdarton The vSphere plugin 2.13 has a facility to define a slave "template", allowing Jenkins to ask for more slaves to satisfy build workload demands. However, the implementation is currently limited to only SSH-launcher slaves (with hard-coded settings too), and with a "retention strategy" limited to only "run one build then dispose of the slave" (with a hard-coded timeout). This has two negative implications: 1) a Windows slave connecting via the Java Web Start method (JNLP) will cause errors in the logs as the SSHLauncher fails to connect. 2) in situations where builds complete quickly, Jenkins can spend longer waiting for each slave to start up than the build takes itself, which isn't very efficient. The docker cloud implementation allows for different launcher methods and different retention strategies - the vSphere plugin should be similarly enhanced to: 1) Allow the slave connection method to be configured, exposing all configuration options for each of the connection methods. 2) Allow the slave "retention strategy" to be configured, exposing all configuration options for each of the connection methods. 3) Add a new strategy (e.g. based on the Jenkins CloudRetentionStrategy) to allow a cloud slave to be reused for multiple builds.
