-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins
Hi! I'm using plugin
http://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin
it is latest version 1.39.
Slave node is Windows 2016R2 and master node is centos6.
When I ran my test by WinRM there was my test took very much time. If i use just JNLP connection protocol tests is take little bit time. There aren't any errors in jobs logs.
Settings for winrm:
winrm set winrm/config/service/Auth @{Basic="true"}
winrm set winrm/config/service @{AllowUnencrypted="true"}
winrm set winrm/config/winrs @{MaxMemoryPerShellMB="1024"}
there is slave server in aws and has m3.medium shape. I'm repeat when I run test via JNLP performance is good.
it is very similare problem https://issues.jenkins-ci.org/browse/JENKINS-32547
There are logs from my job:
*09:40:05* Started by user [Andrei|http://infra1:8080/user/a.zak] *09:40:05* [EnvInject] - Loading node environment variables. *09:43:01* Building remotely on [zak-test (sir-5w48619k)|http://infra1:8080/computer/zak-test%20(sir-5w48619k)] (zak-test) in workspace c:\jenkins\workspace\AT_PES_test_zak -- The process took 10 minutes. -- *09:53:50* Cloning the remote Git repository*09:53:58* Cloning repository git@bitbucket.org:repo/automation.git*09:54:02* > git init c:\jenkins\workspace\AT_PES_test_zak # timeout=10
[JENKINS-53617] Awfull perfomance over winrm.
Description |
Original:
Hi! I'm using plugin [http://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin] it is latest version 1.39. Slave node is Windows 2016R2 and master node is centos6. When I ran my test by WinRM there was my test took very much time. If i use just JNLP connection protocol tests is take little bit time. There aren't any errors in jobs logs. Settings for winrm: winrm set winrm/config/service/Auth @\{Basic="true"} winrm set winrm/config/service @\{AllowUnencrypted="true"} winrm set winrm/config/winrs @\{MaxMemoryPerShellMB="1024"} there is slave server in aws and has m3.medium shape. I'm repeat when I run test via JNLP performance is good. |
New:
Hi! I'm using plugin [http://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin] it is latest version 1.39. Slave node is Windows 2016R2 and master node is centos6. When I ran my test by WinRM there was my test took very much time. If i use just JNLP connection protocol tests is take little bit time. There aren't any errors in jobs logs. Settings for winrm: winrm set winrm/config/service/Auth @\{Basic="true"} winrm set winrm/config/service @\{AllowUnencrypted="true"} winrm set winrm/config/winrs @\{MaxMemoryPerShellMB="1024"} there is slave server in aws and has m3.medium shape. I'm repeat when I run test via JNLP performance is good. it is very similare problem https://issues.jenkins-ci.org/browse/JENKINS-32547  |
Summary | Original: Aufull perfomance over winrm. | New: Awfull perfomance over winrm. |
Description |
Original:
Hi! I'm using plugin [http://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin] it is latest version 1.39. Slave node is Windows 2016R2 and master node is centos6. When I ran my test by WinRM there was my test took very much time. If i use just JNLP connection protocol tests is take little bit time. There aren't any errors in jobs logs. Settings for winrm: winrm set winrm/config/service/Auth @\{Basic="true"} winrm set winrm/config/service @\{AllowUnencrypted="true"} winrm set winrm/config/winrs @\{MaxMemoryPerShellMB="1024"} there is slave server in aws and has m3.medium shape. I'm repeat when I run test via JNLP performance is good. it is very similare problem https://issues.jenkins-ci.org/browse/JENKINS-32547  |
New:
Hi! I'm using plugin [http://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin] it is latest version 1.39. Slave node is Windows 2016R2 and master node is centos6. When I ran my test by WinRM there was my test took very much time. If i use just JNLP connection protocol tests is take little bit time. There aren't any errors in jobs logs. Settings for winrm: winrm set winrm/config/service/Auth @\{Basic="true"} winrm set winrm/config/service @\{AllowUnencrypted="true"} winrm set winrm/config/winrs @\{MaxMemoryPerShellMB="1024"} there is slave server in aws and has m3.medium shape. I'm repeat when I run test via JNLP performance is good. it is very similare problem https://issues.jenkins-ci.org/browse/JENKINS-32547  There are logs from my job: {code:html} *09:40:05* Started by user [Andrei|http://infra1.sche-digi.projects.epam.com:8080/user/a.zakabluk] *09:40:05* [EnvInject] - Loading node environment variables.*09:43:01* Building remotely on [zak-test (sir-5w48619k)|http://infra1.sche-digi.projects.epam.com:8080/computer/zak-test%20(sir-5w48619k)] (zak-test) in workspace c:\jenkins\workspace\AT_PES_test_zak*09:53:50* Cloning the remote Git repository*09:53:58* Cloning repository git@bitbucket.org:schneideripo/pesv2_rangepage_automation.git*09:54:02* > git init c:\jenkins\workspace\AT_PES_test_zak # timeout=10 {code} |
Description |
Original:
Hi! I'm using plugin [http://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin] it is latest version 1.39. Slave node is Windows 2016R2 and master node is centos6. When I ran my test by WinRM there was my test took very much time. If i use just JNLP connection protocol tests is take little bit time. There aren't any errors in jobs logs. Settings for winrm: winrm set winrm/config/service/Auth @\{Basic="true"} winrm set winrm/config/service @\{AllowUnencrypted="true"} winrm set winrm/config/winrs @\{MaxMemoryPerShellMB="1024"} there is slave server in aws and has m3.medium shape. I'm repeat when I run test via JNLP performance is good. it is very similare problem https://issues.jenkins-ci.org/browse/JENKINS-32547  There are logs from my job: {code:html} *09:40:05* Started by user [Andrei|http://infra1.sche-digi.projects.epam.com:8080/user/a.zakabluk] *09:40:05* [EnvInject] - Loading node environment variables.*09:43:01* Building remotely on [zak-test (sir-5w48619k)|http://infra1.sche-digi.projects.epam.com:8080/computer/zak-test%20(sir-5w48619k)] (zak-test) in workspace c:\jenkins\workspace\AT_PES_test_zak*09:53:50* Cloning the remote Git repository*09:53:58* Cloning repository git@bitbucket.org:schneideripo/pesv2_rangepage_automation.git*09:54:02* > git init c:\jenkins\workspace\AT_PES_test_zak # timeout=10 {code} |
New:
Hi! I'm using plugin [http://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin] it is latest version 1.39. Slave node is Windows 2016R2 and master node is centos6. When I ran my test by WinRM there was my test took very much time. If i use just JNLP connection protocol tests is take little bit time. There aren't any errors in jobs logs. Settings for winrm: winrm set winrm/config/service/Auth @\{Basic="true"} winrm set winrm/config/service @\{AllowUnencrypted="true"} winrm set winrm/config/winrs @\{MaxMemoryPerShellMB="1024"} there is slave server in aws and has m3.medium shape. I'm repeat when I run test via JNLP performance is good. it is very similare problem https://issues.jenkins-ci.org/browse/JENKINS-32547  There are logs from my job: {code} *09:40:05* Started by user [Andrei|http://infra1:8080/user/a.zakabluk] *09:40:05* [EnvInject] - Loading node environment variables.*09:43:01* Building remotely on [zak-test (sir-5w48619k)|http://infra1:8080/computer/zak-test%20(sir-5w48619k)] (zak-test) in workspace c:\jenkins\workspace\AT_PES_test_zak*09:53:50* Cloning the remote Git repository*09:53:58* Cloning repository git@bitbucket.org:repo/automation.git*09:54:02* > git init c:\jenkins\workspace\AT_PES_test_zak # timeout=10 {code} |
Description |
Original:
Hi! I'm using plugin [http://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin] it is latest version 1.39. Slave node is Windows 2016R2 and master node is centos6. When I ran my test by WinRM there was my test took very much time. If i use just JNLP connection protocol tests is take little bit time. There aren't any errors in jobs logs. Settings for winrm: winrm set winrm/config/service/Auth @\{Basic="true"} winrm set winrm/config/service @\{AllowUnencrypted="true"} winrm set winrm/config/winrs @\{MaxMemoryPerShellMB="1024"} there is slave server in aws and has m3.medium shape. I'm repeat when I run test via JNLP performance is good. it is very similare problem https://issues.jenkins-ci.org/browse/JENKINS-32547  There are logs from my job: {code} *09:40:05* Started by user [Andrei|http://infra1:8080/user/a.zakabluk] *09:40:05* [EnvInject] - Loading node environment variables.*09:43:01* Building remotely on [zak-test (sir-5w48619k)|http://infra1:8080/computer/zak-test%20(sir-5w48619k)] (zak-test) in workspace c:\jenkins\workspace\AT_PES_test_zak*09:53:50* Cloning the remote Git repository*09:53:58* Cloning repository git@bitbucket.org:repo/automation.git*09:54:02* > git init c:\jenkins\workspace\AT_PES_test_zak # timeout=10 {code} |
New:
Hi! I'm using plugin [http://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin] it is latest version 1.39. Slave node is Windows 2016R2 and master node is centos6. When I ran my test by WinRM there was my test took very much time. If i use just JNLP connection protocol tests is take little bit time. There aren't any errors in jobs logs. Settings for winrm: winrm set winrm/config/service/Auth @\{Basic="true"} winrm set winrm/config/service @\{AllowUnencrypted="true"} winrm set winrm/config/winrs @\{MaxMemoryPerShellMB="1024"} there is slave server in aws and has m3.medium shape. I'm repeat when I run test via JNLP performance is good. it is very similare problem https://issues.jenkins-ci.org/browse/JENKINS-32547  There are logs from my job: {code:java} *09:40:05* Started by user [Andrei|http://infra1:8080/user/a.zak] *09:40:05* [EnvInject] - Loading node environment variables.*09:43:01* Building remotely on [zak-test (sir-5w48619k)|http://infra1:8080/computer/zak-test%20(sir-5w48619k)] (zak-test) in workspace c:\jenkins\workspace\AT_PES_test_zak*09:53:50* Cloning the remote Git repository*09:53:58* Cloning repository git@bitbucket.org:repo/automation.git*09:54:02* > git init c:\jenkins\workspace\AT_PES_test_zak # timeout=10 {code} |
Description |
Original:
Hi! I'm using plugin [http://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin] it is latest version 1.39. Slave node is Windows 2016R2 and master node is centos6. When I ran my test by WinRM there was my test took very much time. If i use just JNLP connection protocol tests is take little bit time. There aren't any errors in jobs logs. Settings for winrm: winrm set winrm/config/service/Auth @\{Basic="true"} winrm set winrm/config/service @\{AllowUnencrypted="true"} winrm set winrm/config/winrs @\{MaxMemoryPerShellMB="1024"} there is slave server in aws and has m3.medium shape. I'm repeat when I run test via JNLP performance is good. it is very similare problem https://issues.jenkins-ci.org/browse/JENKINS-32547  There are logs from my job: {code:java} *09:40:05* Started by user [Andrei|http://infra1:8080/user/a.zak] *09:40:05* [EnvInject] - Loading node environment variables.*09:43:01* Building remotely on [zak-test (sir-5w48619k)|http://infra1:8080/computer/zak-test%20(sir-5w48619k)] (zak-test) in workspace c:\jenkins\workspace\AT_PES_test_zak*09:53:50* Cloning the remote Git repository*09:53:58* Cloning repository git@bitbucket.org:repo/automation.git*09:54:02* > git init c:\jenkins\workspace\AT_PES_test_zak # timeout=10 {code} |
New:
Hi! I'm using plugin [http://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin] it is latest version 1.39. Slave node is Windows 2016R2 and master node is centos6. When I ran my test by WinRM there was my test took very much time. If i use just JNLP connection protocol tests is take little bit time. There aren't any errors in jobs logs. Settings for winrm: winrm set winrm/config/service/Auth @\{Basic="true"} winrm set winrm/config/service @\{AllowUnencrypted="true"} winrm set winrm/config/winrs @\{MaxMemoryPerShellMB="1024"} there is slave server in aws and has m3.medium shape. I'm repeat when I run test via JNLP performance is good. it is very similare problem https://issues.jenkins-ci.org/browse/JENKINS-32547  There are logs from my job: {code:java} *09:40:05* Started by user [Andrei|http://infra1:8080/user/a.zak] *09:40:05* [EnvInject] - Loading node environment variables. *09:43:01* Building remotely on [zak-test (sir-5w48619k)|http://infra1:8080/computer/zak-test%20(sir-5w48619k)] (zak-test) in workspace c:\jenkins\workspace\AT_PES_test_zak -- The process took 10 minutes. -- *09:53:50* Cloning the remote Git repository*09:53:58* Cloning repository git@bitbucket.org:repo/automation.git*09:54:02* > git init c:\jenkins\workspace\AT_PES_test_zak # timeout=10 {code} |