[JIRA] [vmware] (JENKINS-20011) only try to poer on machine if job requests ist
cforce commented on JENKINS-20011 only try to poer on machine if job requests ist I need it to never power on only use if already online. The Problem is i need to disconnect then before 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 -- 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/groups/opt_out.
[JIRA] [vmware] (JENKINS-20011) only try to poer on machine if job requests ist
cforce edited a comment on JENKINS-20011 only try to poer on machine if job requests ist I DO wanna power on the slave, but ONLY if a JOB requests to do it by name or label filter, not because the slave node is just configured. I then DO WANT to use the plugins vmware api features in the job jonfig for this node. Maybe it would makes things clear if you explain if i need to have the node registered as vmware node if i wannan use the vmware features in the job for this node. If not, then you are right - i could use a dumb slave. Tx for pointing things out. 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 -- 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/groups/opt_out.
[JIRA] [vmware] (JENKINS-20011) only try to poer on machine if job requests ist
cforce commented on JENKINS-20011 only try to poer on machine if job requests ist I DO wanna power on the salve, but ONLy i a a JOB requests to do it, not because the slave node is configured to be selectable (by name or label). I then DO WANT to use the plugins vmware api features in the job jonfig for this node. Maybe it would makes thing clear if you make explian if i need to have the node registered as vmware node if i wannan use the vmware features in the job for this node. If not, then you are right i could use a dumb slave. Tx for pointing things out. 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 -- 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/groups/opt_out.
[JIRA] [vmware] (JENKINS-20011) only try to poer on machine if job requests ist
Jason Swager commented on JENKINS-20011 only try to poer on machine if job requests ist Just to confirm - you don't want Jenkins to power the slave on or off, just use the slave if it is online? If this is what you want, then using the vSphere Cloud slave is NOT what you should do. You want to use the Jenkins Dumb Slave - even though the slave is a VM. The Dumb Slave has no capability to turn on or off - it relies on something other than Jenkins (human, timer based power strips, BIOS power timer controls, whatever) to turn the slave on off. If Jenkins sends a job to slave like that, it will just remain in the queue until the slave is powered on and connected. Have you tried just using the Dumb Slave? Recommend giving that a try and seeing how that work for your situation. 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 -- 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/groups/opt_out.
[JIRA] [vmware] (JENKINS-20011) only try to poer on machine if job requests ist
Jason Swager commented on JENKINS-20011 only try to poer on machine if job requests ist If you don't want Jenkins to control the slave as if it where a VM - allowing power-on, power-off, revert on demand - then I would suggest that you don't need the slave to be a vSphere Cloud slave, but just a normal dumb slave. Jenkins lets you create those and leaves the turning on, turning off to you. The intent behind the vSphere Cloud slaves is that Jenkins can control the slave more closely. It sounds like you don't want it to have that degree of control. The dumb slave would probably work better for you. 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 -- 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/groups/opt_out.
[JIRA] [vmware] (JENKINS-20011) only try to poer on machine if job requests ist
cforce commented on JENKINS-20011 only try to poer on machine if job requests ist I do want jenkins to control the slave, but not all teams which have control on the salves have control on jenkins. They want to power off the slave by themself to do restorre from backup's or juts get offline to save hardware ressources fpr some time. Later they start the slave or its backup again. Jenkins shall just use if if its online , also be possible to use the vsphere features then. At the moment the plugin tries to immideatlitly start any slave when it went offline. There is no setting to do nothing in that case. I don't want the slave to be put Offline when jenkins mean not to need it, because this salves are also used by our team, for tesing purposes beyond jenkins jobs running there. Jenkins shall just use it if its online, don't power on or power off, but for any job istself calls it. This is not the case here, it's caused by the standard vsphere node config, where is no option "only to use if online" 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 -- 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/groups/opt_out.
