[JIRA] (JENKINS-60330) EC2 number of instances capped at 1 even though Instance Cap is greater
Title: Message Title George Cimpoies updated JENKINS-60330 Jenkins / JENKINS-60330 EC2 number of instances capped at 1 even though Instance Cap is greater Change By: George Cimpoies Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203341.1575031121000.3631.1578399060586%40Atlassian.JIRA.
[JIRA] (JENKINS-60330) EC2 number of instances capped at 1 even though Instance Cap is greater
Title: Message Title George Cimpoies updated JENKINS-60330 Although AMI instance cap was set to 10, global instance cap was set to 1 Jenkins / JENKINS-60330 EC2 number of instances capped at 1 even though Instance Cap is greater Change By: George Cimpoies Status: Open Fixed but Unreleased Assignee: FABRIZIO MANFREDI George Cimpoies Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60330) EC2 number of instances capped at 1 even though Instance Cap is greater
Title: Message Title George Cimpoies updated an issue Jenkins / JENKINS-60330 EC2 number of instances capped at 1 even though Instance Cap is greater Change By: George Cimpoies Environment: Jenkins 2.187AWS EC2 1.47 (https://github.com/jenkinsci/ec2-plugin/pull/410) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203341.1575031121000.3464.1578386100464%40Atlassian.JIRA.
[JIRA] (JENKINS-60330) EC2 number of instances capped at 1 even though Instance Cap is greater
Title: Message Title
George Cimpoies updated an issue
Jenkins / JENKINS-60330
EC2 number of instances capped at 1 even though Instance Cap is greater
Change By:
George Cimpoies
I'm trying to provision AWS EC2 agents as build slaves for our Jenkins master, whenever a job matching the ami labels (defined in Jenkins config) enters the build queue. Cloud config:!image-2019-11-29-14-35-28-900.png!All the builds that I schedule will wait for the existing AWS node to finish building, even though the Instance Cap is set to 30 (I've tried to tie multiple jobs to the same label and they all wait for the one single node to finish building):!image-2019-11-29-14-36-54-791.png!The job is configured to run concurrent builds:!image-2019-11-29-14-37-36-917.png!In the Jenkins logs I see this recurrently: {code:java}Planned 0 new nodesNov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.NoDelayProvisionerStrategy applyAfter provisioning, available capacity=0, currentDemand=1Nov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.NoDelayProvisionerStrategy applyProvisioning not complete, consulting remaining strategiesNov 29, 2019 1:37:37 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-0266c7b78a0d89503', labels='c42xlarge'}. Attempting to provision slave needed by excess workload of 1 unitsNov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.EC2Cloud countCurrentEC2SlavesCounting current slaves: All AMIS Jenkins Server: http://deb-jenkins-prd.ullink.lan/Nov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.EC2Cloud countCurrentEC2SlavesExisting instance found: i-01e4a3e64c7dac1e7 AMI: ami-0266c7b78a0d89503 Jenkins Server: http://deb-jenkins-prd.ullink.lan/Nov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.EC2Cloud countCurrentEC2SlavesCounting current slaves: AMI: ami-0266c7b78a0d89503 TemplateDesc: AWS Windows Node Jenkins Server: http://deb-jenkins-prd.ullink.lan/Nov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.EC2Cloud countCurrentEC2SlavesExisting instance found: i-01e4a3e64c7dac1e7 AMI: ami-0266c7b78a0d89503 Template: AWS Windows Node Jenkins Server: http://deb-jenkins-prd.ullink.lan/Nov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.EC2Cloud getPossibleNewSlavesCountAvailable Total Slaves: 0 Available AMI slaves: 29 AMI: ami-0266c7b78a0d89503 TemplateDesc: AWS Windows NodeNov 29, 2019 1:37:37 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-0266c7b78a0d89503', labels='c42xlarge'}. Cannot provision - no capacity for instances: 0Nov 29, 2019 1:37:37 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-0266c7b78a0d89503', labels='c42xlarge'}Nov 29, 2019 1:37:46 PM FINE hudson.plugins.ec2.NoDelayProvisionerStrategy applyAvailable capacity=0, currentDemand=1Nov 29, 2019 1:37:47 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-0266c7b78a0d89503', labels='c42xlarge'}. Attempting to provision slave needed by excess workload of 1 unitsNov 29, 2019 1:37:47 PM FINE hudson.plugins.ec2.EC2Cloud countCurrentEC2SlavesCounting
[JIRA] (JENKINS-60330) EC2 number of instances capped at 1 even though Instance Cap is greater
Title: Message Title George Cimpoies updated an issue Jenkins / JENKINS-60330 EC2 number of instances capped at 1 even though Instance Cap is greater Change By: George Cimpoies Attachment: image-2019-11-29-16-09-13-234.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203341.1575031121000.9409.1575036600339%40Atlassian.JIRA.
[JIRA] (JENKINS-60330) EC2 number of instances capped at 1 even though Instance Cap is greater
Title: Message Title George Cimpoies updated an issue Jenkins / JENKINS-60330 EC2 number of instances capped at 1 even though Instance Cap is greater Change By: George Cimpoies Environment: Jenkins 2.187AWS EC2 1.47 (https://github.com/jenkinsci/ec2-plugin/pull/410) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203341.1575031121000.9383.1575033240206%40Atlassian.JIRA.
[JIRA] (JENKINS-60330) EC2 number of instances capped at 1 even though Instance Cap is greater
Title: Message Title
George Cimpoies updated an issue
Jenkins / JENKINS-60330
EC2 number of instances capped at 1 even though Instance Cap is greater
Change By:
George Cimpoies
I'm trying to provision AWS EC2 agents as build slaves for our Jenkins master, whenever a job matching the ami labels (defined in Jenkins config) enters the build queue. Cloud config:!image-2019-11-29-14-35-28-900.png!All the builds that I schedule will wait for the existing AWS node to finish building, even though the Instance Cap is set to 30 (I've tried to tie multiple jobs to the same label and they all wait for the one single node to finish building) :!image-2019-11-29-14-36-54-791.png!The job is configured to run concurrent builds:!image-2019-11-29-14-37-36-917.png!In the Jenkins logs I see this recurrently: {code:java}Planned 0 new nodesNov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.NoDelayProvisionerStrategy applyAfter provisioning, available capacity=0, currentDemand=1Nov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.NoDelayProvisionerStrategy applyProvisioning not complete, consulting remaining strategiesNov 29, 2019 1:37:37 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-0266c7b78a0d89503', labels='c42xlarge'}. Attempting to provision slave needed by excess workload of 1 unitsNov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.EC2Cloud countCurrentEC2SlavesCounting current slaves: All AMIS Jenkins Server: http://deb-jenkins-prd.ullink.lan/Nov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.EC2Cloud countCurrentEC2SlavesExisting instance found: i-01e4a3e64c7dac1e7 AMI: ami-0266c7b78a0d89503 Jenkins Server: http://deb-jenkins-prd.ullink.lan/Nov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.EC2Cloud countCurrentEC2SlavesCounting current slaves: AMI: ami-0266c7b78a0d89503 TemplateDesc: AWS Windows Node Jenkins Server: http://deb-jenkins-prd.ullink.lan/Nov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.EC2Cloud countCurrentEC2SlavesExisting instance found: i-01e4a3e64c7dac1e7 AMI: ami-0266c7b78a0d89503 Template: AWS Windows Node Jenkins Server: http://deb-jenkins-prd.ullink.lan/Nov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.EC2Cloud getPossibleNewSlavesCountAvailable Total Slaves: 0 Available AMI slaves: 29 AMI: ami-0266c7b78a0d89503 TemplateDesc: AWS Windows NodeNov 29, 2019 1:37:37 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-0266c7b78a0d89503', labels='c42xlarge'}. Cannot provision - no capacity for instances: 0Nov 29, 2019 1:37:37 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-0266c7b78a0d89503', labels='c42xlarge'}Nov 29, 2019 1:37:46 PM FINE hudson.plugins.ec2.NoDelayProvisionerStrategy applyAvailable capacity=0, currentDemand=1Nov 29, 2019 1:37:47 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-0266c7b78a0d89503', labels='c42xlarge'}. Attempting to provision slave needed by excess workload of 1 unitsNov 29, 2019 1:37:47 PM FINE hudson.plugins.ec2.EC2Cloud countCurrentEC2SlavesCounting
[JIRA] (JENKINS-60330) EC2 number of instances capped at 1 even though Instance Cap is greater
Title: Message Title
George Cimpoies updated an issue
Jenkins / JENKINS-60330
EC2 number of instances capped at 1 even though Instance Cap is greater
Change By:
George Cimpoies
I'm trying to provision AWS EC2 agents as build slaves for our Jenkins master, whenever a job matching the ami labels ( dedined defined in Jenkins config) enters the build queue. Cloud config:!image-2019-11-29-14-35-28-900.png!All the builds that I schedule will wait for the existing AWS node to finish building, even though the Instance Cap is set to 30:!image-2019-11-29-14-36-54-791.png!The job is configured to run concurrent builds:!image-2019-11-29-14-37-36-917.png!In the Jenkins logs I see this recurrently: {code:java}Planned 0 new nodesNov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.NoDelayProvisionerStrategy applyAfter provisioning, available capacity=0, currentDemand=1Nov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.NoDelayProvisionerStrategy applyProvisioning not complete, consulting remaining strategiesNov 29, 2019 1:37:37 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-0266c7b78a0d89503', labels='c42xlarge'}. Attempting to provision slave needed by excess workload of 1 unitsNov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.EC2Cloud countCurrentEC2SlavesCounting current slaves: All AMIS Jenkins Server: http://deb-jenkins-prd.ullink.lan/Nov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.EC2Cloud countCurrentEC2SlavesExisting instance found: i-01e4a3e64c7dac1e7 AMI: ami-0266c7b78a0d89503 Jenkins Server: http://deb-jenkins-prd.ullink.lan/Nov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.EC2Cloud countCurrentEC2SlavesCounting current slaves: AMI: ami-0266c7b78a0d89503 TemplateDesc: AWS Windows Node Jenkins Server: http://deb-jenkins-prd.ullink.lan/Nov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.EC2Cloud countCurrentEC2SlavesExisting instance found: i-01e4a3e64c7dac1e7 AMI: ami-0266c7b78a0d89503 Template: AWS Windows Node Jenkins Server: http://deb-jenkins-prd.ullink.lan/Nov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.EC2Cloud getPossibleNewSlavesCountAvailable Total Slaves: 0 Available AMI slaves: 29 AMI: ami-0266c7b78a0d89503 TemplateDesc: AWS Windows NodeNov 29, 2019 1:37:37 PM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-0266c7b78a0d89503', labels='c42xlarge'}. Cannot provision - no capacity for instances: 0Nov 29, 2019 1:37:37 PM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-0266c7b78a0d89503', labels='c42xlarge'}Nov 29, 2019 1:37:46 PM FINE hudson.plugins.ec2.NoDelayProvisionerStrategy applyAvailable capacity=0, currentDemand=1Nov 29, 2019 1:37:47 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-0266c7b78a0d89503', labels='c42xlarge'}. Attempting to provision slave needed by excess workload of 1 unitsNov 29, 2019 1:37:47 PM FINE hudson.plugins.ec2.EC2Cloud countCurrentEC2SlavesCounting current slaves: All AMIS Jenkins Server: http://deb-jenkins-prd.ullink.lan/Nov 29, 2019 1:37:47 PM FINE
[JIRA] (JENKINS-60330) EC2 number of instances capped at 1 even though Instance Cap is greater
Title: Message Title
George Cimpoies created an issue
Jenkins / JENKINS-60330
EC2 number of instances capped at 1 even though Instance Cap is greater
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Attachments:
image-2019-11-29-14-34-52-692.png, image-2019-11-29-14-35-28-900.png, image-2019-11-29-14-36-49-367.png, image-2019-11-29-14-36-54-791.png, image-2019-11-29-14-37-36-917.png
Components:
ec2-plugin
Created:
2019-11-29 12:38
Environment:
Jenkins 2.187 AWS EC2 1.47
Priority:
Blocker
Reporter:
George Cimpoies
I'm trying to provision AWS EC2 agents as build slaves for our Jenkins master, whenever a job matching the ami labels (dedined in Jenkins config) enters the build queue. Cloud config: All the builds that I schedule will wait for the existing AWS node to finish building, even though the Instance Cap is set to 30: The job is configured to run concurrent builds: In the Jenkins logs I see this recurrently:
Planned 0 new nodes
Nov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.NoDelayProvisionerStrategy applyAfter provisioning, available capacity=0, currentDemand=1
Nov 29, 2019 1:37:37 PM FINE hudson.plugins.ec2.NoDelayProvisionerStrategy applyProvisioning not complete, consulting remaining strategies
Nov 29, 2019 1:37:37 PM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-0266c7b78a0d89503', labels='c42xlarge'}. Attempting to provision slave needed by excess
[JIRA] (JENKINS-51581) Add option to override tool config for slave nodes created by EC2 plugin
Title: Message Title George Cimpoies commented on JENKINS-51581 Re: Add option to override tool config for slave nodes created by EC2 plugin Pull request created: https://github.com/jenkinsci/ec2-plugin/pull/410 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190974.1527594894000.5054.1570719060188%40Atlassian.JIRA.
[JIRA] (JENKINS-51581) Add option to override tool config for slave nodes created by EC2 plugin
Title: Message Title George Cimpoies updated an issue Jenkins / JENKINS-51581 Add option to override tool config for slave nodes created by EC2 plugin Change By: George Cimpoies Environment: Jenkins 2.107.3, Amazon EC2 Plugin 1. 39 46.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190974.1527594894000.4559.1570703704058%40Atlassian.JIRA.
[JIRA] (JENKINS-51581) Add option to override tool config for slave nodes created by EC2 plugin
Title: Message Title
George Cimpoies edited a comment on JENKINS-51581
Re: Add option to override tool config for slave nodes created by EC2 plugin
This is a show-stopper for us as we want to rely solely on aws for our build agents, but we can't define global tool locations since we have many different jobs and configurations on Jenkins.With hardware nodes we use swarm plugin + a script like this:{code:java}"$($env:JDK8_PATH)\bin\java.exe" `-cp "$($env:USERPROFILE)\slave.jar" `-jar "$($env:USERPROFILE)\swarm-client.jar" `- deleteExistingClients `-name "$($env:HOSTNAME)" `-disableClientsUniqueId `- fsroot "$($env:USERPROFILE)" `-description "$($env:JENKINS_NODE_DESCRIPTION)" `-master "$($env:JENKINS_MASTER)" `-executors "$($env:JENKINS_NUMBER_OF_EXECUTORS)" `-labels "$($env:JENKINS_NODE_LABELS)" `--toolLocation "jdk7=$($env:JDK7_PATH)" `--toolLocation "jdk8=$($env:JDK8_PATH)" `--toolLocation "jdk9=$($env:JDK9_PATH)" `--toolLocation "jdk10=$($env:JDK10_PATH)" `--toolLocation "jdk11=$($env:JDK11_PATH)" `{code}to add the tool locations on the node that's connecting to Jenkins.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190974.1527594894000.4551.1570703703400%40Atlassian.JIRA.
[JIRA] (JENKINS-51581) Add option to override tool config for slave nodes created by EC2 plugin
Title: Message Title George Cimpoies updated an issue Jenkins / JENKINS-51581 Add option to override tool config for slave nodes created by EC2 plugin Change By: George Cimpoies Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190974.1527594894000.4556.1570703703958%40Atlassian.JIRA.
[JIRA] (JENKINS-51581) Add option to override tool config for slave nodes created by EC2 plugin
Title: Message Title George Cimpoies commented on JENKINS-51581 Re: Add option to override tool config for slave nodes created by EC2 plugin This is a show-stopper for us as we want to rely solely on aws for our build agents, but we can't define global tool locations since we have many different jobs and configurations on Jenkins. With hardware nodes we use swarm plugin + a script like this: "$($env:JDK8_PATH)\bin\java.exe" ` -cp "$($env:USERPROFILE)\slave.jar" ` -jar "$($env:USERPROFILE)\swarm-client.jar" ` -deleteExistingClients ` -name "$($env:HOSTNAME)" ` -disableClientsUniqueId ` -fsroot "$($env:USERPROFILE)" ` -description "$($env:JENKINS_NODE_DESCRIPTION)" ` -master "$($env:JENKINS_MASTER)" ` -executors "$($env:JENKINS_NUMBER_OF_EXECUTORS)" ` -labels "$($env:JENKINS_NODE_LABELS)" ` --toolLocation "jdk7=$($env:JDK7_PATH)" ` --toolLocation "jdk8=$($env:JDK8_PATH)" ` --toolLocation "jdk9=$($env:JDK9_PATH)" ` --toolLocation "jdk10=$($env:JDK10_PATH)" ` --toolLocation "jdk11=$($env:JDK11_PATH)" ` to add the tool locations on the node that's connecting to Jenkins. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-51581) Add option to override tool config for slave nodes created by EC2 plugin
Title: Message Title George Cimpoies updated an issue Jenkins / JENKINS-51581 Add option to override tool config for slave nodes created by EC2 plugin Change By: George Cimpoies Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190974.1527594894000.4542.1570703460398%40Atlassian.JIRA.
[JIRA] (JENKINS-59682) EC2 Plugin terminates windows instance right after connecting when using ssh.
Title: Message Title George Cimpoies closed an issue as Not A Defect Jenkins / JENKINS-59682 EC2 Plugin terminates windows instance right after connecting when using ssh. Change By: George Cimpoies Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202380.157043884.4194.1570691760623%40Atlassian.JIRA.
[JIRA] (JENKINS-59682) EC2 Plugin terminates windows instance right after connecting when using ssh.
Title: Message Title George Cimpoies commented on JENKINS-59682 Re: EC2 Plugin terminates windows instance right after connecting when using ssh. Raihaan Shouhell works perfectly after overriding the temp directory. I'll close the issue. Just out of curiosity, is there any other option to force the plugin to connect to a windows node through ssh, other than setting the ami type to unix? (even though the ami is actually windows). Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202380.157043884.4192.1570691760581%40Atlassian.JIRA.
[JIRA] (JENKINS-59682) EC2 Plugin terminates windows instance right after connecting when using ssh.
Title: Message Title George Cimpoies updated an issue Jenkins / JENKINS-59682 EC2 Plugin terminates windows instance right after connecting when using ssh. Change By: George Cimpoies Comment: [~raihaan] you are correct, I want to force the connection to be via ssh(even if the node is a windows one). Where is the temp directory located? I can't find any configuration related to the temp directory on Jenkins' side.Thanks in advance! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202380.157043884.3151.1570516860201%40Atlassian.JIRA.
[JIRA] (JENKINS-59682) EC2 Plugin terminates windows instance right after connecting when using ssh.
Title: Message Title George Cimpoies edited a comment on JENKINS-59682 Re: EC2 Plugin terminates windows instance right after connecting when using ssh. [~raihaan] you are correct, I want to force the connection to be via ssh(even if the node is a windows one). Where is the temp directory located? I can't find any configuration related to the temp directory on Jenkins' side. Thanks in advance! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202380.157043884.3143.1570515720246%40Atlassian.JIRA.
[JIRA] (JENKINS-59682) EC2 Plugin terminates windows instance right after connecting when using ssh.
Title: Message Title George Cimpoies commented on JENKINS-59682 Re: EC2 Plugin terminates windows instance right after connecting when using ssh. Raihaan Shouhell you are correct, I want to force the connection to be via ssh(even if the node is a windows one). Where is the temp directory located? Thanks in advance! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202380.157043884.3141.1570515240364%40Atlassian.JIRA.
[JIRA] (JENKINS-59682) EC2 Plugin terminates windows instance right after connecting when using ssh.
Title: Message Title
George Cimpoies updated an issue
Jenkins / JENKINS-59682
EC2 Plugin terminates windows instance right after connecting when using ssh.
Change By:
George Cimpoies
{code:java}collapseBuild Executor StatusOct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Launching instance: i-0b3686cd8938dd562Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: bootstrap()Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Getting keypair...Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Using private key jenkins-builder (SHA-1 fingerprint f3:b6:14:0d:dd:ef:5e:4a:30:e8:3e:47:6f:30:46:f4:b6:dc:8a:b0)Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Authenticating as clujOct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:54:35 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:54:35 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:54:40 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:54:50 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:54:50 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:54:55 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:05 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:55:05 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:55:10 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:20 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:55:20 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:55:25 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:27 AM hudson.plugins.ec2.EC2CloudINFO: Connected via SSH.Oct 07, 2019 10:55:27 AM hudson.plugins.ec2.EC2CloudINFO: connect fresh as rootOct 07, 2019 10:55:28 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:28 AM hudson.plugins.ec2.EC2CloudINFO: Connected via SSH.Oct 07, 2019 10:55:29 AM hudson.plugins.ec2.EC2CloudINFO: Creating tmp directory (/tmp) if it does not existThe syntax of the command is incorrect.Oct 07, 2019 10:55:29 AM hudson.plugins.ec2.EC2CloudINFO: Verifying: java -fullversionjava full version "1.8.0_131-b11"Oct 07, 2019 10:55:31 AM hudson.plugins.ec2.EC2CloudINFO: Verifying: which scp/usr/bin/scpOct 07, 2019 10:55:32 AM hudson.plugins.ec2.EC2CloudINFO: Copying remoting.jar to: /tmpOct 07, 2019 10:55:33 AM hudson.plugins.ec2.EC2CloudINFO: Launching remoting agent (via Trilead
[JIRA] (JENKINS-59682) EC2 Plugin terminates windows instance right after connecting when using ssh.
Title: Message Title
George Cimpoies updated an issue
Jenkins / JENKINS-59682
EC2 Plugin terminates windows instance right after connecting when using ssh.
Change By:
George Cimpoies
{code:java}collapseBuild Executor StatusOct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Launching instance: i-0b3686cd8938dd562Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: bootstrap()Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Getting keypair...Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Using private key jenkins-builder (SHA-1 fingerprint f3:b6:14:0d:dd:ef:5e:4a:30:e8:3e:47:6f:30:46:f4:b6:dc:8a:b0)Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Authenticating as clujOct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:54:35 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:54:35 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:54:40 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:54:50 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:54:50 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:54:55 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:05 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:55:05 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:55:10 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:20 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:55:20 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:55:25 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:27 AM hudson.plugins.ec2.EC2CloudINFO: Connected via SSH.Oct 07, 2019 10:55:27 AM hudson.plugins.ec2.EC2CloudINFO: connect fresh as rootOct 07, 2019 10:55:28 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:28 AM hudson.plugins.ec2.EC2CloudINFO: Connected via SSH.Oct 07, 2019 10:55:29 AM hudson.plugins.ec2.EC2CloudINFO: Creating tmp directory (/tmp) if it does not existThe syntax of the command is incorrect.Oct 07, 2019 10:55:29 AM hudson.plugins.ec2.EC2CloudINFO: Verifying: java -fullversionjava full version "1.8.0_131-b11"Oct 07, 2019 10:55:31 AM hudson.plugins.ec2.EC2CloudINFO: Verifying: which scp/usr/bin/scpOct 07, 2019 10:55:32 AM hudson.plugins.ec2.EC2CloudINFO: Copying remoting.jar to: /tmpOct 07, 2019 10:55:33 AM hudson.plugins.ec2.EC2CloudINFO: Launching remoting agent (via Trilead
[JIRA] (JENKINS-59682) EC2 Plugin terminates windows instance right after connecting when using ssh.
Title: Message Title
George Cimpoies updated an issue
Jenkins / JENKINS-59682
EC2 Plugin terminates windows instance right after connecting when using ssh.
Change By:
George Cimpoies
{code:java}collapseBuild Executor StatusOct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Launching instance: i-0b3686cd8938dd562Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: bootstrap()Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Getting keypair...Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Using private key jenkins-builder (SHA-1 fingerprint f3:b6:14:0d:dd:ef:5e:4a:30:e8:3e:47:6f:30:46:f4:b6:dc:8a:b0)Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Authenticating as clujOct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:54:35 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:54:35 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:54:40 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:54:50 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:54:50 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:54:55 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:05 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:55:05 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:55:10 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:20 AM hudson.plugins.ec2.EC2CloudINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Oct 07, 2019 10:55:20 AM hudson.plugins.ec2.EC2CloudINFO: Waiting for SSH to come up. Sleeping 5.Oct 07, 2019 10:55:25 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:27 AM hudson.plugins.ec2.EC2CloudINFO: Connected via SSH.Oct 07, 2019 10:55:27 AM hudson.plugins.ec2.EC2CloudINFO: connect fresh as rootOct 07, 2019 10:55:28 AM hudson.plugins.ec2.EC2CloudINFO: Connecting to 10.230.0.233 on port 22, with timeout 1.Oct 07, 2019 10:55:28 AM hudson.plugins.ec2.EC2CloudINFO: Connected via SSH.Oct 07, 2019 10:55:29 AM hudson.plugins.ec2.EC2CloudINFO: Creating tmp directory (/tmp) if it does not existThe syntax of the command is incorrect.Oct 07, 2019 10:55:29 AM hudson.plugins.ec2.EC2CloudINFO: Verifying: java -fullversionjava full version "1.8.0_131-b11"Oct 07, 2019 10:55:31 AM hudson.plugins.ec2.EC2CloudINFO: Verifying: which scp/usr/bin/scpOct 07, 2019 10:55:32 AM hudson.plugins.ec2.EC2CloudINFO: Copying remoting.jar to: /tmpOct 07, 2019 10:55:33 AM hudson.plugins.ec2.EC2CloudINFO: Launching remoting agent (via Trilead
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title George Cimpoies commented on JENKINS-58193 Re: EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version Raihaan Shouhell sure, I've documented everything here: https://issues.jenkins-ci.org/browse/JENKINS-59682 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200248.1561491352000.3110.1570509720403%40Atlassian.JIRA.
[JIRA] (JENKINS-59682) EC2 Plugin terminates windows instance right after connecting when using ssh.
Title: Message Title George Cimpoies commented on JENKINS-59682 Re: EC2 Plugin terminates windows instance right after connecting when using ssh. According to https://issues.jenkins-ci.org/browse/JENKINS-58193 the issue was released in 1.44.2, but it is reproducible with version 1.46.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202380.157043884.2345.1570439100319%40Atlassian.JIRA.
[JIRA] (JENKINS-59682) EC2 Plugin terminates windows instance right after connecting when using ssh.
Title: Message Title George Cimpoies updated an issue Jenkins / JENKINS-59682 EC2 Plugin terminates windows instance right after connecting when using ssh. Change By: George Cimpoies Attachment: Capture.PNG Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202380.157043884.2339.1570439041651%40Atlassian.JIRA.
[JIRA] (JENKINS-59682) EC2 Plugin terminates windows instance right after connecting when using ssh.
Title: Message Title George Cimpoies updated an issue Jenkins / JENKINS-59682 EC2 Plugin terminates windows instance right after connecting when using ssh. Change By: George Cimpoies Attachment: Capture3.PNG Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202380.157043884.2343.1570439042398%40Atlassian.JIRA.
[JIRA] (JENKINS-59682) EC2 Plugin terminates windows instance right after connecting when using ssh.
Title: Message Title George Cimpoies updated an issue Jenkins / JENKINS-59682 EC2 Plugin terminates windows instance right after connecting when using ssh. Change By: George Cimpoies Attachment: Capture2.PNG Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202380.157043884.2341.1570439041902%40Atlassian.JIRA.
[JIRA] (JENKINS-59682) EC2 Plugin terminates windows instance right after connecting when using ssh.
Title: Message Title George Cimpoies updated an issue Jenkins / JENKINS-59682 EC2 Plugin terminates windows instance right after connecting when using ssh. Change By: George Cimpoies Attachment: Capture3.PNG Attachment: Capture2.PNG Attachment: Capture.PNG Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202380.157043884.2337.1570439041341%40Atlassian.JIRA.
[JIRA] (JENKINS-59682) EC2 Plugin terminates windows instance right after connecting when using ssh.
Title: Message Title George Cimpoies created an issue Jenkins / JENKINS-59682 EC2 Plugin terminates windows instance right after connecting when using ssh. Issue Type: Bug Assignee: FABRIZIO MANFREDI Attachments: Capture.PNG, Capture2.PNG, Capture3.PNG Components: ec2-plugin Created: 2019-10-07 09:00 Environment: EC2 Plugin 1.46.1 Jenkins 2.187 Priority: Blocker Reporter: George Cimpoies collapseBuild Executor Status Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2Cloud INFO: Launching instance: i-0b3686cd8938dd562 Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2Cloud INFO: bootstrap() Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2Cloud INFO: Getting keypair... Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2Cloud INFO: Using private key jenkins-builder (SHA-1 fingerprint f3:b6:14:0d:dd:ef:5e:4a:30:e8:3e:47:6f:30:46:f4:b6:dc:8a:b0) Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2Cloud INFO: Authenticating as cluj Oct 07, 2019 10:54:25 AM hudson.plugins.ec2.EC2Cloud INFO: Connecting to 10.230.0.233 on port 22, with timeout 1. Oct 07, 2019 10:54:35 AM hudson.plugins.ec2.EC2Cloud INFO: Failed to connect via ssh: The kexTimeout (1 ms) expired. Oct 07, 2019 10:54:35 AM hudson.plugins.ec2.EC2Cloud INFO: Waiting for SSH to come up. Sleeping 5. Oct 07, 2019 10:54:40 AM hudson.plugins.ec2.EC2Cloud INFO: Connecting to 10.230.0.233 on port 22, with timeout 1. Oct 07, 2019 10:54:50
[JIRA] (JENKINS-58193) EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title George Cimpoies commented on JENKINS-58193 Re: EC2 Plguin: EC2 instances are getting terminated right away on initializing in 1.44 version tapvir virk FABRIZIO MANFREDI, was this released? I'm encountering it on version 1.46.1 as well. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200248.1561491352000.2310.1570438320710%40Atlassian.JIRA.
[JIRA] (JENKINS-59579) EC2 Plugin stops slave when build is running
Title: Message Title George Cimpoies closed an issue as Not A Defect Jenkins / JENKINS-59579 EC2 Plugin stops slave when build is running Change By: George Cimpoies Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202219.1569824606000.8619.1569929520202%40Atlassian.JIRA.
[JIRA] (JENKINS-59390) EC2 slave disconnects with EOFException
Title: Message Title George Cimpoies commented on JENKINS-59390 Re: EC2 slave disconnects with EOFException I have the same issue, might want to check the logs of your master Jenkins, in mine I have: Oct 01, 2019 10:53:45 AM INFO hudson.plugins.ec2.EC2RetentionStrategy internalCheck Idle timeout of [instance name] after 31 idle minutes, instance statusRUNNING Oct 01, 2019 10:53:45 AM INFO hudson.plugins.ec2.EC2AbstractSlave idleTimeout EC2 instance idle time expired: i-07625ee50b5a21bde Oct 01, 2019 10:53:45 AM INFO hudson.plugins.ec2.EC2OndemandSlave terminate Terminated EC2 instance (terminated): i-07625ee50b5a21bde Oct 01, 2019 10:53:45 AM INFO hudson.plugins.ec2.EC2OndemandSlave terminate Removed EC2 instance from jenkins master: i-07625ee50b5a21bde So nodes are automatically disconnected after an idle timeout, I've raised a similar issue here: https://issues.jenkins-ci.org/browse/JENKINS-59579 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit
[JIRA] (JENKINS-59579) EC2 Plugin stops slave when build is running
Title: Message Title
George Cimpoies updated an issue
Jenkins / JENKINS-59579
EC2 Plugin stops slave when build is running
Change By:
George Cimpoies
I have set up the connection between Jenkins and AWS via Amazon EC2 plugin. Jenkins master cloud config: !Capture.PNG!!Capture2.PNG!!Capture3.PNG|width=1016,height=736! The node connects via the Amazon plugin and then creates a new connection via Swarm plugin and the job ends up running on the connection made through swarm. (This is because my jobs include TestComplete & FlaUI and winRM is not quite suited for their requirements). Jobs that take under 25 min run successfully, anything that goes over 25-26 min fails with the following: Slave log:{code:java}12:49:46 java.io.IOException: Backing channel 'JNLP4-connect connection from 10.230.0.101/10.230.0.101:49724' is disconnected.12:49:46 at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:214)12:49:46 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)12:49:46 at com.sun.proxy.$Proxy89.isAlive(Unknown Source)12:49:46 at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1172)12:49:46 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1164)12:49:46 at hudson.Launcher$ProcStarter.join(Launcher.java:492)12:49:46 at hudson.plugins.gradle.Gradle.performTask(Gradle.java:333)12:49:46 at hudson.plugins.gradle.Gradle.perform(Gradle.java:225)12:49:46 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)12:49:46 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)12:49:46 at hudson.model.Build$BuildExecution.build(Build.java:206)12:49:46 at hudson.model.Build$BuildExecution.doRun(Build.java:163)12:49:46 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)12:49:46 at hudson.model.Run.execute(Run.java:1815)12:49:46 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)12:49:46 at hudson.model.ResourceController.execute(ResourceController.java:97)12:49:46 at hudson.model.Executor.run(Executor.java:429)12:49:46 Caused by: java.nio.channels.ClosedChannelException12:49:46 at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)12:49:46 at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179)12:49:46 at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)12:49:46 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)12:49:46 at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)12:49:46 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)12:49:46 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)12:49:46 at java.lang.Thread.run(Thread.java:748){code}On the master's log I can see:{code:java}Idle timeout of EC2 (Itiviti AWS) - Windows Jenkins node autoconnecting to deb-jenkins-prd using Swarm plugin
[JIRA] (JENKINS-59579) EC2 Plugin stops slave when build is running
Title: Message Title
George Cimpoies updated an issue
Jenkins / JENKINS-59579
EC2 Plugin stops slave when build is running
Change By:
George Cimpoies
Summary:
Amazon EC2 Plugin stops slave idle timeout, where to find it and how to increase it? when build is running
Issue Type:
New Feature Bug
Priority:
Major Blocker
I have set up the connection between Jenkins and AWS via Amazon EC2 plugin. Jenkins master cloud config: !Capture.PNG!!Capture2.PNG!!Capture3.PNG|width=1016,height=736! The node connects via the Amazon plugin and then creates a new connection via Swarm plugin and the job ends up running on the connection made through swarm. (This is because my jobs include TestComplete & FlaUI and winRM is not quite suited for their requirements). Jobs that take under 25 min run successfully, anything that goes over 25-26 min fails with the following: Slave log: {code:java}12:49:46 java.io.IOException: Backing channel 'JNLP4-connect connection from 10.230.0.101/10.230.0.101:49724' is disconnected.12:49:46 at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:214)12:49:46 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)12:49:46 at com.sun.proxy.$Proxy89.isAlive(Unknown Source)12:49:46 at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1172)12:49:46 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1164)12:49:46 at hudson.Launcher$ProcStarter.join(Launcher.java:492)12:49:46 at hudson.plugins.gradle.Gradle.performTask(Gradle.java:333)12:49:46 at hudson.plugins.gradle.Gradle.perform(Gradle.java:225)12:49:46 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)12:49:46 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)12:49:46 at hudson.model.Build$BuildExecution.build(Build.java:206)12:49:46 at hudson.model.Build$BuildExecution.doRun(Build.java:163)12:49:46 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)12:49:46 at hudson.model.Run.execute(Run.java:1815)12:49:46 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)12:49:46 at hudson.model.ResourceController.execute(ResourceController.java:97)12:49:46 at hudson.model.Executor.run(Executor.java:429)12:49:46 Caused by: java.nio.channels.ClosedChannelException12:49:46 at
[JIRA] (JENKINS-46505) Jenkins slaves are being stopped multiple times with ec2 plugin
Title: Message Title George Cimpoies commented on JENKINS-46505 Re: Jenkins slaves are being stopped multiple times with ec2 plugin I'm having the same issue but in my case any build taking over 30 min is broken because the node is shut down no matter what... Any ideas? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184821.1503942227000.8493.1569920520252%40Atlassian.JIRA.
[JIRA] (JENKINS-59579) Amazon slave idle timeout, where to find it and how to increase it?
Title: Message Title
George Cimpoies updated an issue
Jenkins / JENKINS-59579
Amazon slave idle timeout, where to find it and how to increase it?
Change By:
George Cimpoies
Issue Type:
Bug New Feature
Priority:
Blocker Major
I have set up the connection between Jenkins and AWS via Amazon EC2 plugin. Jenkins master cloud config: !Capture.PNG!!Capture2.PNG!!Capture3.PNG|width=1016,height=736! The node connects via the Amazon plugin and then creates a new connection via Swarm plugin and the job ends up running on the connection made through swarm. (This is because my jobs include TestComplete & FlaUI and winRM is not quite suited for their requirements). Jobs that take under 25 min run successfully, anything that goes over 25-26 min fails with the following: {code:java}12:49:46 java.io.IOException: Backing channel 'JNLP4-connect connection from 10.230.0.101/10.230.0.101:49724' is disconnected.12:49:46 at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:214)12:49:46 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)12:49:46 at com.sun.proxy.$Proxy89.isAlive(Unknown Source)12:49:46 at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1172)12:49:46 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1164)12:49:46 at hudson.Launcher$ProcStarter.join(Launcher.java:492)12:49:46 at hudson.plugins.gradle.Gradle.performTask(Gradle.java:333)12:49:46 at hudson.plugins.gradle.Gradle.perform(Gradle.java:225)12:49:46 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)12:49:46 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)12:49:46 at hudson.model.Build$BuildExecution.build(Build.java:206)12:49:46 at hudson.model.Build$BuildExecution.doRun(Build.java:163)12:49:46 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)12:49:46 at hudson.model.Run.execute(Run.java:1815)12:49:46 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)12:49:46 at hudson.model.ResourceController.execute(ResourceController.java:97)12:49:46 at hudson.model.Executor.run(Executor.java:429)12:49:46 Caused by: java.nio.channels.ClosedChannelException12:49:46 at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)12:49:46 at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179)12:49:46 at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)12:49:46 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)12:49:46 at
[JIRA] (JENKINS-59579) Amazon slave idle timeout, where to find it and how to increase it?
Title: Message Title George Cimpoies updated an issue Jenkins / JENKINS-59579 Amazon slave idle timeout, where to find it and how to increase it? Change By: George Cimpoies Summary: Amazon nodes automatically disconnect from Master after a period of time slave idle timeout, where to find it and how to increase it? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202219.1569824606000.7587.1569826440150%40Atlassian.JIRA.
[JIRA] (JENKINS-59579) Amazon nodes automatically disconnect from Master after a period of time
Title: Message Title George Cimpoies created an issue Jenkins / JENKINS-59579 Amazon nodes automatically disconnect from Master after a period of time Issue Type: Bug Assignee: FABRIZIO MANFREDI Attachments: Capture.PNG, Capture2.PNG, Capture3.PNG Components: ec2-plugin, swarm-plugin Created: 2019-09-30 06:23 Environment: Jenkins 2.187 Amazon EC2 1.44.1 Swarm 3.13 Priority: Blocker Reporter: George Cimpoies I have set up the connection between Jenkins and AWS via Amazon EC2 plugin. Jenkins master cloud config: The node connects via the Amazon plugin and then creates a new connection via Swarm plugin and the job ends up running on the connection made through swarm. (This is because my jobs include TestComplete & FlaUI and winRM is not quite suited for their requirements). Jobs that take under 25 min run successfully, anything that goes over 25-26 min fails with the following: 12:49:46 java.io.IOException: Backing channel 'JNLP4-connect connection from 10.230.0.101/10.230.0.101:49724' is disconnected. 12:49:46 at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:214) 12:49:46 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283) 12:49:46 at com.sun.proxy.$Proxy89.isAlive(Unknown Source) 12:49:46 at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1172) 12:49:46 at
[JIRA] (JENKINS-59150) Jenkins LTS 2.176.x logs about the new Stapler routing rules have erroneous information
Title: Message Title George Cimpoies updated an issue Jenkins / JENKINS-59150 Jenkins LTS 2.176.x logs about the new Stapler routing rules have erroneous information Change By: George Cimpoies Summary: Upgrading to Jenkins LTS 2.176.x documentation has logs about the new Stapler routing rules have erroneous information Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201586.1567168518000.3266.1567168680161%40Atlassian.JIRA.
[JIRA] (JENKINS-59150) Upgrading to Jenkins LTS 2.176.x documentation has erroneous information
Title: Message Title George Cimpoies created an issue Jenkins / JENKINS-59150 Upgrading to Jenkins LTS 2.176.x documentation has erroneous information Issue Type: Improvement Assignee: rsandell Components: core, gerrit-trigger-plugin Created: 2019-08-30 12:35 Environment: Jenkins LTS 2.176.x Priority: Minor Reporter: George Cimpoies After upgrading to Jenkins LTS 2.176, the Server Status page in Gerrit Trigger section didn't display any information, showing a "Data error" message. Logs: 2019-08-30 09:47:15.644+ [id=65732] WARNING j.s.s.StaplerFilteredActionListener#onGetterTrigger: New Stapler routing rules result in the URL "/gerrit-trigger/serverStatuses" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "method com.sonyericsson.hudson.plugins.gerrit.trigger.GerritManagement getServerStatuses". Learn more: https://jenkins.io/redirect/stapler-routing The line method com.sonyericsson.hudson.plugins.gerrit.trigger.GerritManagement getServerStatuses is wrong, because it doesn't work upon testing. Instead, the correct line to be added to the whitelist is
[JIRA] (JENKINS-56271) xUnit produce an empty report for NUnit3 type
Title: Message Title George Cimpoies commented on JENKINS-56271 Re: xUnit produce an empty report for NUnit3 type Nikolas Falco I think there's a small mistake, the fix is actually in version 2.3.2 according to the commits and not 2.3.2, right? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197843.155110973.25008.1560249720200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54860) As a vSphere cloud plugin user, I cannot create VM from Jenkins pipeline because template does not have snapshot, not possible in vSphere Version 6.5.0 Build 7070488
Title: Message Title George Cimpoies commented on JENKINS-54860 Re: As a vSphere cloud plugin user, I cannot create VM from Jenkins pipeline because template does not have snapshot, not possible in vSphere Version 6.5.0 Build 7070488 Hi pjdarton! To my understanding, a template can't have snapshots so the exception shouldn't be thrown. Only VMs can have snapshots, templates can't. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54860) As a vSphere cloud plugin user, I cannot create VM from Jenkins pipeline because template does not have snapshot, not possible in vSphere Version 6.5.0 Build 7070488
Title: Message Title George Cimpoies updated an issue Jenkins / JENKINS-54860 As a vSphere cloud plugin user, I cannot create VM from Jenkins pipeline because template does not have snapshot, not possible in vSphere Version 6.5.0 Build 7070488 Change By: George Cimpoies Priority: Critical Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54860) As a vSphere cloud plugin user, I cannot create VM from Jenkins pipeline because template does not have snapshot, not possible in vSphere Version 6.5.0 Build 7070488
Title: Message Title
George Cimpoies updated an issue
Jenkins / JENKINS-54860
As a vSphere cloud plugin user, I cannot create VM from Jenkins pipeline because template does not have snapshot, not possible in vSphere Version 6.5.0 Build 7070488
Change By:
George Cimpoies
I'm trying to create a VM from template via Jenkins pipeline using the following code {code:java} _node node () { _ _vSphere vSphere buildStep: [$class: 'Clone', clone: 'windwaker-gccloned', powerOn: false, sourceName: 'windwaker-gc', datastore:'Datastore2_Dev_Qa', resourcePool:'Normal'], serverName:'vcr-dev' _ _ } _ {code} The code fails with the following exception: {code:java} * ERROR: vSphere Error: Source Template "windwaker-gc" requires at least one snapshot. * {code} This was supposed to be fixed in https://issues.jenkins-ci.org/browse/JENKINS-24661
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-54860) As a vSphere cloud plugin user, I cannot create VM from Jenkins pipeline because template does not have snapshot, not possible in vSphere Version 6.5.0 Build 7070488
Title: Message Title
George Cimpoies updated an issue
Jenkins / JENKINS-54860
As a vSphere cloud plugin user, I cannot create VM from Jenkins pipeline because template does not have snapshot, not possible in vSphere Version 6.5.0 Build 7070488
Change By:
George Cimpoies
I'm trying to create a VM from template via Jenkins pipeline using the following code_node() {_ _vSphere buildStep: [$class: 'Clone', clone: 'windwaker-gccloned', powerOn: false, sourceName: 'windwaker-gc', datastore:'Datastore2_Dev_Qa', resourcePool:'Normal'], serverName:'vcr-dev'__}_ The code fails with the following exception: *ERROR: vSphere Error: Source VM Template "windwaker-gc" requires at least one snapshot.* This was supposed to be fixed in https://issues.jenkins-ci.org/browse/JENKINS-24661
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-54860) As a vSphere cloud plugin user, I cannot create VM from Jenkins pipeline because template does not have snapshot, not possible in vSphere Version 6.5.0 Build 7070488
Title: Message Title
George Cimpoies created an issue
Jenkins / JENKINS-54860
As a vSphere cloud plugin user, I cannot create VM from Jenkins pipeline because template does not have snapshot, not possible in vSphere Version 6.5.0 Build 7070488
Issue Type:
Bug
Assignee:
Unassigned
Components:
vsphere-cloud-plugin
Created:
2018-11-26 13:07
Environment:
Jenkins Jenkins v. 2.130 vSphere v. 6.5.0 Build 7070488 vSphere cloud plugin v. 2.18
Priority:
Critical
Reporter:
George Cimpoies
I'm trying to create a VM from template via Jenkins pipeline using the following code node() { vSphere buildStep: [$class: 'Clone', clone: 'windwaker-gccloned', powerOn: false, sourceName: 'windwaker-gc', datastore:'Datastore2_Dev_Qa', resourcePool:'Normal'], serverName:'vcr-dev' } The code fails with the following exception: ERROR: vSphere Error: Source VM "windwaker-gc" requires at least one snapshot. This was supposed to be fixed in https://issues.jenkins-ci.org/browse/JENKINS-24661
Add Comment
